Hi
VX debugger don't find prg.
My config is :

Alaska
	\projets
	\sources (prg)
	\resource
	\runtime
	\xppw32
but VX store only relative path to prg. It can create the exe but not 
compile.
I need urgent help.
Regards.

  Christian Laborde
GTS Gestion-Technologie-Services

Route de la Corniche, 1
CH 1096 Cully
Suisse

"Christian Laborde" <infolab@bluewin.ch> wrote in message
news:n1sNqUn3DHA.2016@S15147418...

Christian,

erm, ... what exactly is your problem?

> VX debugger don't find prg.
(...)
> but VX store only relative path to prg. It can create the
> exe but not compile.

You mean you can compile your project but can't debug
it?

I'm sorry but I we need a bit more info here:
  o where's your project located?
  o where's your .EXE located?
  o can't you compile or can't you debug?

Regards,
  Till

--
---------------------------------------------------
ARD - Alaska Research & Development

Web:       http://www.alaska-research.com
Investors: http://www.alaska-research.com/tifund
E-Mail:    mailto:till.warweg@alaska-research.com
Contact:   mailto:info@alaska-research.com
---------------------------------------------------

My config is :
\Alaska
     \projets (xpj)
     \sources (prg)
     \resource
     \runtime
     \xppw32
	   \...
So VX compile and link but the debugger can't file the prg.
Look at attachment.
VX store only relative path to prg, but relative to what ?
And how VX do resolve it ?
Regards

  Christian Laborde
GTS Gestion-Technologie-Services

Route de la Corniche, 1
CH 1096 Cully
Suisse

Hi Christian,

 > My config is :
 > \Alaska
 >     \projets (xpj)
 >     \sources (prg)
 >     \resource
 >     \runtime
 >     \xppw32
and   \obj
and   f:\abax2\sys\convabx.exe

Let me step in here since this is not really a debugger issue.

To your first question why the debugger can't find the exe.
This is because the target is linked to f:\apbax\sys.
The debugger does not expect the target there since VX
does not take care of the /out flag, it is simply forwarded
to the linker. The debugger then expects the target in
projects directory.

You can resolve this by loading the target with File->open
dialog. VX then unloads the project file and creates a new
project under f:\apbax\sys\convabx.xpj. This project is solely
used for running the debugger and storing debugger information
like breakpoints and watchpoints.

To your second question about the relative pathes: They are
always relative to the position of the project file.

The problem you encounter here is already reported by other
users. It is difficult to handle an environment where the
target must reside at a location where VX does not expect it.

We plan to resolve this issue in the next release that will be
out at the beginning of February. There you will have more
control where the target is.

Christian Laborde wrote:
> My config is :
> \Alaska
>     \projets (xpj)
>     \sources (prg)
>     \resource
>     \runtime
>     \xppw32
>        \...
> So VX compile and link but the debugger can't file the prg.
> Look at attachment.
> VX store only relative path to prg, but relative to what ?
> And how VX do resolve it ?
> Regards
> 
> 
> ------------------------------------------------------------------------
> 
> [PROJECT]
>     DEBUG         = yes
>     VERSION       = 2.0
>     OPENFILES     = \ALASKA\SOURCE\BASES\CONVABX.PRG;..\SOURCE\BASES\CONVABX.PRG
>     CONVABX.XPJ
> 
> [CONVABX.XPJ]
>     CONVABX.EXE
> 
> [CONVABX.EXE]
>     COMPILE       = xpp
>     COMPILE_FLAGS = /wu /q
>     DEBUG_SAVE    = yes
>     GUI           = yes
>     LINKER        = alink
>     LINK_FLAGS    = /out:f:\abax2\sys\convabx.exe
>     RC_COMPILE    = arc
>     RC_FLAGS      = /v
>     OBJ_DIR       = d:\alaska\obj
>  $START-AUTODEPEND
>     ..\RESOURCE\CONVABX.RES
>     STD.CH
>     SET.CH
>     NATMSG.CH
>     GET.CH
>     PROMPT.CH
>     MEMVAR.CH
>     COLLAT.CH
>     ADSMG.CH
>     ADSMGMT.CH
>     INKEY.CH
>     XBTSYS.CH
>     FILEIO.CH
>     INFOLAB.CH
>     DIRECTRY.CH
>     XBP.CH
>     ERROR.CH
>     XB2.CH
>     CONVABX.obj
>     DBESYS.obj
>     ERRORSYS.obj
>  $STOP-AUTODEPEND
>     ..\OBJ\BIN2NUM.OBJ
>     ..\RESOURCE\CONVABX.ARC
>     GTSLIB4.LIB
>     ..\SOURCE\BASES\CONVABX.PRG
>     ..\SOURCE\GTSLIB\DBESYS.PRG
>     ..\SOURCE\GTSLIB\ERRORSYS.PRG
> 
> 
> 
> ------------------------------------------------------------------------
> 

Regards
   Andreas Herdt
   [Alaska Research & Development]