Fix examples for Windows. #14
Conversation
This fixes a linking issue with integers, and updates the Python code to run the correct interpreter and use the proper DLL names. # `integers` The problem here is that, on Windows, if you don't use any symbols from the standard library *and* create a dynamic library, linking will fail. This is a known issue (rust-lang/rust#18807) and the only half-way decent solution is to include a dead function that *does* use something from the standard library. # Python Two changes. First, I've added a hashbang to invoke the correct Python interpreter. On Windows, it's common to execute scripts directly without specifying the interpreter. In addition, it is *not* common to have multiple versions of Python accessible on the PATH at one time. As such, Python on Windows comes with a "launcher" that reads the hashbang and executes the appropriate version of Python. Anyone with Python 3.x installed will almost certainly have *that* as the default, so indicating that the script needs Python 2.x specifically is a really good idea. Also, the existing examples do not correctly determine the name of the Windows libraries being loaded. Two things: they end in `.dll` and they *do not* start with `lib`.
|
Thanks for the updates! The Rust issue is an interesting one, and I might need to start a "gotchas" page to catalog items like that.
Maybe a word went missing here? I'm not sure what you are referring to with "these". I'll merge these after I have a better understanding of what's broken 😃 |
|
Oh, whoops; the "Miscellaneous" header used to be "Ruby", but then I added the stuff about doc changes, so I changed it and forgot to adjust the existing paragraph. To be clear: the Ruby examples segfault. The C and Python ones work fine. :P |
|
OK. Since I don't have much ability of automated testing on Windows, I'm afraid those will always be second-class citizens. Having some Windows knowledge is hopefully better than none, thanks! |
This fixes a linking issue with integers, and updates the Python code
to run the correct interpreter and use the proper DLL names.
integersThe problem here is that, on Windows, if you don't use any symbols from
the standard library and create a dynamic library, linking will fail.
This is a known issue (rust-lang/rust#18807) and the only half-way decent
solution is to include a dead function that does use something from the
standard library.
Python
Two changes. First, I've added a hashbang to invoke the correct Python
interpreter. On Windows, it's common to execute scripts directly without
specifying the interpreter. In addition, it is not common to have
multiple versions of Python accessible on the PATH at one time. As such,
Python on Windows comes with a "launcher" that reads the hashbang and
executes the appropriate version of Python.
Anyone with Python 3.x installed will almost certainly have that as the
default, so indicating that the script needs Python 2.x specifically is
a really good idea.
Also, the existing examples do not correctly determine the name of the
Windows libraries being loaded. Two things: they end in
.dlland theydo not start with
lib.Miscellaneous
I have made no attempt to get these working on Windows, as the examples just immediately segfault for no apparent reason and, to be honest, I don't care enough about Ruby to work out why. :P
I'm also working on doc changes separately.