Viktor Szakáts wrote:
>
>> 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.
>
> No problem, but even in this case, the best solution
> is to setup PATH properly for given compiler and let
> hbmk2 autodetect compiler.
>
> HB_COMPILER is _only_ necessary if there are multiple
> C compiler present in the PATH at the same time.
>
> If that tells anything, on Windows I compile for
> practically all possible Harbour targets and I never
> touch HB_COMPILER.
>
We can document it or omit it altogether. But I had some issues
in the past. I do not remember exactly what these were but
soon I will experiment when I will turn to building refinements
scheduled next week.
Virtually, only C compiler specific path should go inside it,
rest hbMK2 should take care, this is the goal for Harbour projects.
-----
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http://n2.nabble.com/HBIDE-Project-build-start-folder-problem-tp4861627p4873743.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
