>> 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.
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. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
