[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] Launching CDT on Windows
|
The good news is that I'm giving a tutorial at EclipseCon on how you can
create your own integration like the MinGW one. (shameless plug ;).
Cheers,
Doug.
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mike Wrighton
> Sent: Friday, January 16, 2009 10:28 AM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Launching CDT on Windows
>
> Ah ok. We're using our own toolchain (gcc based).
>
> 2009/1/16 Schaefer, Doug <Doug.Schaefer@xxxxxxxxxxxxx>:
> > When you select the MinGW toolchain in the build settings, the CDT
> > sets the path automatically before invoking the compiler or calling
> > make. You didn't say what toolchain you are using but I'd
> ask whoever
> > gave it to you for the same. Mind you, you may not get it. But, you
> > can do this yourself manually by changing the PATH variable in the
> > Environment tab of your build settings.
> >
> > The idea is to be able to support multiple toolchains, i.e.
> multiple
> > things call gcc, in the same workspace, or project even.
> Assuming the
> > compiler is in your PATH ahead of time prevents things like that.
> >
> > At any rate, to answer your original question, there is no standard
> > way to launch the CDT on Windows in the way you are
> suggesting, mainly
> > because it isn't recommended.
> >
> > Doug.
> >
> >> -----Original Message-----
> >> From: cdt-dev-bounces@xxxxxxxxxxx
> >> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mike Wrighton
> >> Sent: Friday, January 16, 2009 10:04 AM
> >> To: CDT General developers list.
> >> Subject: Re: [cdt-dev] Launching CDT on Windows
> >>
> >> Sorry I wasn't that clear, I was mainly talking about having the
> >> compiler etc in the PATH environment variable prior to running
> >> Eclipse (prior to running java anyway, since you can't modify the
> >> environment from Java as far as I know). In wascana I assume the
> >> launcher executable sets the environment?
> >>
> >> Doug - I'm not sure what you meant about the build integration?
> >>
> >>
> >> 2009/1/16 Schaefer, Doug <Doug.Schaefer@xxxxxxxxxxxxx>:
> >> >> -----Original Message-----
> >> >> From: cdt-dev-bounces@xxxxxxxxxxx
> >> >> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Subs
> >> >> Sent: Friday, January 16, 2009 7:02 AM
> >> >> To: CDT General developers list.
> >> >> Subject: Re: [cdt-dev] Launching CDT on Windows
> >> >>
> >> >> Mike Wrighton wrote:
> >> >> > Kind of a question on product deployment I suppose, but
> >> is there a
> >> >> > standard way of launching CDT from Windows? Usually a set of
> >> >> > environment variables need to be set prior to launching
> >> it, so I've
> >> >> > always used batch files with desktop shortcuts which has
> >> >> always seemed
> >> >> > a bit naff??
> >> >> >
> >> >> > Cheers,
> >> >> > Mike
> >> >> > _______________________________________________
> >> >> > cdt-dev mailing list
> >> >> > cdt-dev@xxxxxxxxxxx
> >> >> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >> >> >
> >> >> Eh?
> >> >>
> >> >> I have *no* enviroment variables, batch files, or
> anything. I just
> >> >> run eclipse.
> >> >
> >> > Same with Wascana, the CDT for Windows distro on
> >> sourceforge. I have a
> >> > build integration for the MinGW environment that sets the env
> >> > variables for me. You can also set the manually in the
> >> build properties.
> >> >
> >> > Doug
> >> > _______________________________________________
> >> > 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
>