Barry Jackson wrote:
>
> [ COMMON ]
> PLATFORM = linux
> COMPILER = gcc
>
> [GCC]
> {hb_comp} gcc
> 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
>
My fault, sorry.
[ COMMON ]
PLATFORM = linux
COMPILER = gcc
[GCC]
{hb_comp} gcc
{content} export HB_COMPILER=gcc
{content} export PATH=$PATH:/home/baz/SVN/harbour/bin/linux/gcc
{content} export PATH=$PATH:/home/baz/SVN/harbour/lib/linux/gcc
{content} export PATH=$PATH:/home/baz/SVN/harbour/include
{content} export PATH=$PATH:/usr/bin/gcc:/usr/lib/gcc
To debug more:
::cBatch := ::oEV:prepareBatch( ::cWrkEnvironment )
1. Check what is the value of ::cWrkEnvironment
2. Check what is the value of ::cBatch ( a temporary file name )
3. Explore what is wrong with idemisc.prg line#2070 function
hbide_getShellCommandTempFile()
Until this temp file containg above entries is not there and executed
by the shell, hbIDE will be unable to locate environment components.
To debug, you can use standard method, say, MsgBox() or whatever
you employ for debugging.
This call creates a temporary shell command file having entries in
{content} lines above.
-----
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http://n2.nabble.com/HBIDE-Project-build-start-folder-problem-tp4861627p4867582.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
