Re: Re: Importing external dependencies into source

Okay this helped. IndigoStar's User Manual gives the command for compiling an external file into the exe. Yahoo!

Okay, there is another extension to this problem. find.exe is also a windows application. Previously, to get my script to find the GNU version BEFORE the windows version I had to put the directory of the GNU find earlier in my "path" environment variable.

I've now run and tested the new compiled version and it appears to have imported the GNU find.exe into the exe. Yay! Small win. BUT ... taking it to another box, having no actual directory in which the GNU version of find sits how can I get my script to use it? It appears to look for the windows "find.exe" when it makes the call to find. I can see by the error message generated its using Windows "find.exe" but the exe of my script has the GNU find compiled into it. Help?!

Thanks
Dean

Programming these days takes more than a lone avenger with a compiler. - sam

Comment on Re: Re: Importing external dependencies into source

Replies are listed 'Best First'.
Re: Re: Re: Importing external dependencies into source by arden (Curate) on Mar 03, 2004 at 18:00 UTC
crabbdean, don't call it by `system('find','arg1','arg2');` but call it with `system('/dir/to/find','arg1','arg2');` or `system('./find','arg1','arg2');` so that you don't have to worry about the system using it's own version of find. This, of course, assumes that you know where it puts your find.exe file. Look at the docs and see how to use `bind`ed files. . . - - arden.	[reply] [d/l] [select]