Viktor Szakáts wrote:
>
>>>> export HB_COMPILER=gcc
>>>> export PATH=$PATH:/home/baz/SVN/harbour/bin/linux/gcc
>>>> export PATH=$PATH:/home/baz/SVN/harbour/lib/linux/gcc
>>>> export PATH=$PATH:/home/baz/SVN/harbour/include
>>>> export PATH=$PATH:/usr/bin/gcc:/usr/lib/gcc
>
> BTW, all of the above is not necessary for hbmk2.
> (given that gcc is already in the PATH, which it
> is on most systems)
>
> So I'd suggest not to confuse matters with these
> unnecessary lines. In fact it's outright dangerous.
>
> For hbmk2, it's enough to put in the PATH, or
> refer to it with an absolute name (f.e. /home/me/harbour/bin/hbmk2)
> and it will find everything automatically.
>
> Even HB_COMPILER=gcc is totally unnecessary.
>
You are right when we assume that there is only ONE
environment developer needs or have set his desktop from the
very begining and he donot want to compile with another compiler
or other type of project. In that case there is absolutely no need
to even touch hbide.env. Without any anvironment set, hbIDE only
executes the hbMK2 with its parameters and under the environemnt
hbMK2 detects automatically.
But what if someone wants to experiment with different
compilers and different type of projects, just like in my case.
There comes the concept of hbide.env. For example,
I compile my ERP solutions "Vouch" with MSVC, BCC, MINGW and
OpenWatcome. I never leave the interface even once. I just
change the environment and there it goes.
If you said that, you must be having a broader view of the issue,
I am sure, but still my reasoning is valid. This is not imposed
on the user, this is suggested if he ever want to maintain
many projects, all built under different environmrnts.
-----
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http://n2.nabble.com/HBIDE-Project-build-start-folder-problem-tp4861627p4873116.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
