PB/DLL: command line and output directory

[Dominic Mitchell]

Bernard,
I misread your first reply. What you suggested in your second reply is the
best solution. You can accomplish the same thing from Windows by using
ShellExecute or ShellExecuteEx.

Thanks.


------------------
Dominic Mitchell

[Bernard Chapman]

I just put this in a batch file:

f:
cd\winit
\pbdll50\bin\pbdll \pbdll50\samples\mycode\datacapt /I/pbdll50/winapi;/pbdll50/samples/mycode

First two lines determine the drive and directory.

A click on a desktop (or MS office toolbar) icon does the lot.

You can also add commands to compile the resources before hand if necessary

Bern


------------------
Bern

www.insighttrading.com.au

[Semen Matusovski]

> Maurice, That is not an option.

Why ? UltraEdit, for example, allows to set working directory

------------------
E-MAIL: [email protected]

[Dominic Mitchell]

Maurice,
That is not an option.

Lance,
That is one of the options I was considering. I don't like it because I will
have to modify source files.
No big deal. I will just move the output.

------------------
Dominic Mitchell

[Lance Edmonds]

You can put a path+filename into the #COMPILE EXE metastatement and the compiler will produce the EXE at that location, thus:

#COMPILE EXE "C:\DISTRIB\MYAPP.EXE"

However, the LOG file (/L option) will remain in the current directory as usual.



------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

[Maurice de Laat]

Don't know if such a command exists, but could you try starting
the exe in the directory where you want the results to be written
to?

[Dominic Mitchell]

Given the following

pbdll.exe /ic:\pbdll50\winapi;e:\pbdll\test\bin /l e:\pbdll\test\bin\CodeEdit.bas

Is there a command line switch that will direct the compiler to
put the results in a directory other than the one it resides in?

------------------
Dominic Mitchell