Link error in Xailer portable

[DC]

Hi,
I was able to get Xailer Portable working on a flash drive, on a single
PC, by activating via email.
I'll try it on other PCs later this evening. Meantime, there's an error
when linking a project:
Linking: ProjectName.exe...
Fatal: Unable to open file 'PROJECTNAME.DBJ'.
How do you trace through the compiling and linking step? Is there a
command line you can use, to substitute for Xailer's Project/Build?
It must be an error related to Borland's command line compiler/linker,
but the error doesn't specify that. I've tried going into
Tools/Options/Directories/BCC++, and setting the Borland executables
path to 1) The flash drive and 2) The main hard drive. Same result on both.
xHarbour is also installed on the flash drive, and is set in Options.

[ignacio]

DC escribió el lun, 16 mayo 2011 18:06How do you trace through the compiling and linking step? Is there a
command line you can use, to substitute for Xailer's Project/Build?

Compile with Shift+F9
Regards,

[DC]

On 5/16/2011 12:18 PM, Ignacio Ortiz de Zúñiga wrote:
> DC escribió el lun, 16 mayo 2011 18:06
>> How do you trace through the compiling and linking step?
>> Is there a command line you can use, to substitute for Xailer's
>> Project/Build?
>
>
> Compile with Shift+F9
>
> Regards,
Yep, I see it, ilink32 -Gn -Tpe -x -aa @link.tmp
iLink32 is definitely there, and the link gets executed. It just
doesn't generate any OBJs or DBJs.
Perhaps link.tmp isn't getting generated. It is not in the Recycle bin,
after the link executes. Both a TMP and TEMP environmental variable is
set, if that's needed.
If you think of anything else, please let me know. This is clearly
going to be a very convenient mode of development.
I'll re-look at the settings on the desktop, where it works fine.

[DC]

By the way, the C source files are being generated by xHarbour. It's
only the linking step, that is an obstacle.
On 5/16/2011 12:43 PM, DC wrote:
> On 5/16/2011 12:18 PM, Ignacio Ortiz de Zúñiga wrote:
>> DC escribió el lun, 16 mayo 2011 18:06
>>> How do you trace through the compiling and linking step?
>>> Is there a command line you can use, to substitute for Xailer's
>>> Project/Build?
>>
>>
>> Compile with Shift+F9
>>
>> Regards,
>
> Yep, I see it, ilink32 -Gn -Tpe -x -aa @link.tmp
>
> iLink32 is definitely there, and the link gets executed. It just doesn't
> generate any OBJs or DBJs.
>
> Perhaps link.tmp isn't getting generated. It is not in the Recycle bin,
> after the link executes. Both a TMP and TEMP environmental variable is
> set, if that's needed.
>
> If you think of anything else, please let me know. This is clearly going
> to be a very convenient mode of development.
>
>
> I'll re-look at the settings on the desktop, where it works fine.
>

[ignacio]

DC escribió el lun, 16 mayo 2011 18:45By the way, the C source files are being generated by xHarbour. It's
only the linking step, that is an obstacle.>
Try to delete the file ilink32.cfg on your Bccbin directory, so Xailer can recreate it.
Regards,

[DC]

Definitely progress, now, thanks.
It's now giving linking errors, on missing gtgui.lib. I removed that
from Project Properties/Libraries, then linked again.
Then it reported a missing ZLIB.LIB. I removed that from the Libraries
list, and now how receive a whole bunch of external functions missing.
Ok, I'll copy over the missing libs from the desktop pc, then recheck
them and try again.
On 5/16/2011 1:13 PM, Ignacio Ortiz de Zúñiga wrote:
> DC escribió el lun, 16 mayo 2011 18:45
>> By the way, the C source files are being generated by
>> xHarbour. It's only the linking step, that is an obstacle.>
>
>
> Try to delete the file ilink32.cfg on your Bccbin
> directory, so Xailer can recreate it.
>
> Regards,

[DC]

Better, much better, thanks Ignacio.
On 5/16/2011 1:13 PM, Ignacio Ortiz de Zúñiga wrote:
> DC escribió el lun, 16 mayo 2011 18:45
>> By the way, the C source files are being generated by
>> xHarbour. It's only the linking step, that is an obstacle.>
>
>
> Try to delete the file ilink32.cfg on your Bccbin
> directory, so Xailer can recreate it.
>
> Regards,

[DC]

Forgot to mention - last week, I tried Xailer Portable on several PCs,
after activating them by email (not via the Internet option).
It works great, very convenient, thanks.
On 5/16/2011 12:06 PM, DC wrote:
> Hi,
>
> I was able to get Xailer Portable working on a flash drive, on a single
> PC, by activating via email.
>
> I'll try it on other PCs later this evening. Meantime, there's an error
> when linking a project:
>
> Linking: ProjectName.exe...
> Fatal: Unable to open file 'PROJECTNAME.DBJ'.
>
>
>
> How do you trace through the compiling and linking step? Is there a
> command line you can use, to substitute for Xailer's Project/Build?
>
>
> It must be an error related to Borland's command line compiler/linker,
> but the error doesn't specify that. I've tried going into
> Tools/Options/Directories/BCC++, and setting the Borland executables
> path to 1) The flash drive and 2) The main hard drive. Same result on both.
>
> xHarbour is also installed on the flash drive, and is set in Options.
>
>
>
>