Wascana installed from p2 repo still requires PATH setting

[kaesler]

I wanted to use CDT+Mingw from my x64 Eclipse so I installed it from
the p2 repo. After some trial and error I found that it required me to
set my PATH so that g++ would be found. Would be nice if that were not
necessary, given that the compiler bits are installed "internally"
into Eclipse's install tree. Not a big deal, but it did slow me down a
bit while getting set up.

Thanks again for packaging this for us Eclipse C++ users.

[moldrien]

On 1 nov, 14:34, kaesler <kevin.es...@gmail.com> wrote:
> I wanted to use CDT+Mingw from my x64 Eclipse so I installed it from
> the p2 repo. After some trial and error I found that it required me to
> set my PATH so that g++ would be found. Would be nice if that were not
> necessary, given that the compiler bits are installed "internally"
> into Eclipse's install tree. Not a big deal, but it did slow me down a
> bit while getting set up.
>

Try this:

http://sourceforge.net/projects/wascana/

I've installed several times, and the only choice you have to do is a
directory. In this directory the whole wascana will be installed.
After installation process you can start writing programs without
worryng about g++ path. I've even done that in a pen-drive.

Once installed, it will ask for a path, but for projects.

Regards

[Joel]

I just went through this with a whole classroom of students. On
windows 7, installing eclipse with CDT to C:\eclipse and then
installing wascana from inside eclipse, eclipse CAN NOT compile C++
code. Not until you manually edit the Path environment variable.

Students using XP worked fine.

Something is wrong with the wascana package.

Joel

[Kevin Esler]

That'w what I saw too. I.e. I had the problem on Windows 7.

--
Kevin Esler
Bedford MA, USA

+1-781-330-0325

[Doug Schaefer]

That's very odd since Wascana was created on Windows 7. Are you
selecting the MinGW toolchain when you create new projects?

[Fernando Poza Saura]

Hi again. Happy new year to everyone.

2011/1/7 Doug Schaefer <cdt...@gmail.com>

That's very odd since Wascana was created on Windows 7. Are you
selecting the MinGW toolchain when you create new projects?

The link I sent takes you to an auto-exe file. With it, you don't have to care about selecting the toolchain. It comes with MinGW one inside. It's all packed up so everything is installed in its proper site.

>> I just went through this with a whole classroom of students.  On
>> windows 7, installing eclipse with CDT to C:\eclipse and then
>> installing wascana from inside eclipse, eclipse CAN NOT compile C++
>> code.  Not until you manually edit the Path environment variable.

I think this is done through the opcion update > install (or something) in eclipse platform, isn't it?.
This is not the solution I suggested. As stated above you don't need (actually, probably is better not to have) a previous eclipse installation in your computer.

So, my experience is that in windows XP this package works great. I've not idea about windows vista or 7 (and, so far, I don't feel very curious about it ;-)  )

Regards.
Fernando

[yk]

interestingly enough, installation from setup program works. however,
i was not able to figure out where path is appended

On Jan 13, 3:50 am, Fernando Poza Saura

<fernando.poza.sa...@gmail.com> wrote:
> Hi again. Happy new year to everyone.
>

> 2011/1/7 Doug Schaefer <cdtd...@gmail.com>

[yk]

I did selected MinGW.
as soon as i modify PATH on the OS level everything works. what does
not work are modifications on workspace pr project level. BTW, i do
not have previous version, 2 version (wascana and soa can coexist in
different directories)