Got side tracked a little by an ugly scanner discovery bug but will get to this right after.
Sent from my BlackBerry 10 smartphone.
Hi Doug,
any success about this?
Thanks
Marc
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
> Sent: Thursday, December 20, 2012 11:49 AM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] gdb for testing on hudson
>
> On 12-12-20 11:44 AM, "Marc Khouzam"
> wrote:
>
> >
> >> -----Original Message-----
> >> From: cdt-dev-bounces@xxxxxxxxxxx
> >> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
> >> Sent: Thursday, December 20, 2012 11:25 AM
> >> To: CDT General developers list.
> >> Subject: Re: [cdt-dev] gdb for testing on hudson
> >>
> >> That only holds for that shell, not the maven job.
> >>
> >> I don't mind adding a property. Do know off hand where this
> >> check is made?
> >
> >The name of the gdb binary to be used is set in:
> >org.eclipse.cdt.tests.dsf.gdb.framework.BaseTestCase#setGdbPr
> ogramNamesLau
> >nchAttributes()
> >
> >Thinking about it, using a property would allow people to
> leave their PATH
> >alone and use the property themselves.
>
> Definitely a positive side effect of this.
>
> >
> >Another option that was suggested to me was to have maven
> download the
> >pre-built
> >gdb from some location. This would make the solution
> slave-independent.
> >But
> >where to store this gdb so it could be downloaded...
>
> All slaves can see our staging directory where the final bits
> are placed
> so that should be safe.
>
> >
> >The property sounds like a quick and good solution.
> >
> >Thanks for taking care of this!
>
> No problem. We need to step up our involvement in this to
> make sure our
> user base is happy with our common debugger experience.
>
> >
> >Marc
> >
> >>
> >> On 12-12-20 11:20 AM, "Marc Khouzam"
> >> wrote:
> >>
> >> >Thanks Doug!
> >> >
> >> >As you mention, the JUnit tests look for gdb in PATH. The
> >> name of GDB
> >> >must include the version.
> >> >If you installed gdb 7.5 or 7.5.1, gdb must be named gdb.7.5
> >> >
> >> >How about adding a build step in Hudson to "Execute shell"
> >> and set the
> >> >PATH variable?
> >> >
> >> >Marc
> >> >
> >> >
> >> >
> >> >________________________________
> >> >
> >> > From: cdt-dev-bounces@xxxxxxxxxxx
> >> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> >> >On Behalf Of Doug Schaefer
> >> > Sent: Thursday, December 20, 2012 11:04 AM
> >> > To: CDT General developers list.
> >> > Subject: [cdt-dev] gdb for testing on hudson
> >> >
> >> >
> >> > This is mainly for Marc but I'm sure others are interested too.
> >> >
> >> > I've *finally* got gdb built so that it can run on the
> >> Eclipse servers.
> >> >They run SuSE linux which is just different enough to make
> >> it complicated.
> >> >
> >> > At any rate, how do I now integrate it into our build?
> >> Setting the path
> >> >is going to be complicated in Hudson. Do we have a property
> >> I can set to
> >> >point at it? Should we add one?
> >> >
> >> > Thanks!
> >> > :D
> >> >
> >> >_______________________________________________
> >> >cdt-dev mailing list
> >> >cdt-dev@xxxxxxxxxxx
> >> >https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >>
> >> _______________________________________________
> >> cdt-dev mailing list
> >> cdt-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >>
> >_______________________________________________
> >cdt-dev mailing list
> >cdt-dev@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
