1. Binding with win32lib?
Hi, I was playing around with win32lib awhile back, very untrue to my
nature, actually finished something :) The only problem I have, is that I
seem, either in my normal confusion or even worse confusion caused by the
flu, to be unable to bind it
The process to do so is to simply use fix.ex on the file that is to be
bound, and then to run bind on it, using the clear routines option, right?
Or am I missing something?
Also, does anyone know if there is a page out there with older versions of
win32lib uploaded?
Thanks for the help everyone! Hopefully I won't be horribly embarrassed by
my ignorance once this flu wears off ^^
2. Re: Binding with win32lib?
- Posted by David Cuny <dcuny at LANSET.COM>
Oct 07, 1999
-
Last edited Oct 08, 1999
Naflign wrote:
> The process to do so is to simply use fix.ex on the file that
> is to be bound, and then to run bind on it, using the clear
> routines option, right?
If you are attempting to bind the file and Euphoria complains that there are
name conflicts, you can use fix.ex to create a bindable version of the
program. For example, if you had a file called 'myprog.exw', you could type:
ex fix myprog.exw tmp.exw
Will create a program called 'tmp.exw' from the source file 'program.exw',
with all the naming conflicts removed. Unlike bind, the fix program will
also take care of references inside of routine_id(), assuming that they are
quoted routine names. You can the bind the new file:
bindw -clear_routines tmp.exw
and rename the executable:
rename tmp.exe program.exe
It's a bit roundabout, but it works.
>Also, does anyone know if there is a page out there with older versions of
>win32lib uploaded?
You can find a couple versions back (but not too far) on my page at:
www.lanset.com/dcuny/euphoria.htm
Previous to that, I don't have any versions, although I might add some if
there is demand for it.
Good luck with the flu!
-- David Cuny
