lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

I've been happily using my Lua + C bit string module in various Unix
environments. Now I'd like to add it to test code under Windows, using
LfW and os.execute() when any of our external programs are needed. Most
of what I need is already present (and working) in LfW; I just need to
compile my bstring C code in a manner suitable for use with it. We still
use VC++ 6.0 but I will happily download one of the Microsoft Express

I'd appreciate a link to a quick how-to for building LfW-compatible DLLs
and Lua modules. A pointer to the build process for one of the included
libraries will probably suffice.

I didn't see any developer info in the documentation for LfW
nor at It's certainly possible that
I missed it. I had remembered a more recent discussion, but the latest
message that I found using the lual-l archive search was:

Are the instructions mentioned above still applicable? I see only
VC++-2008 Express at the referenced Microsoft web site (for convenience,
it's, but that's
redirected). Do I use 2008, somehow targeted for the 2005 run-time?

By the way, I have found LfW to be excellent. I love the debugging
capability. I only wish I had Emacs integrated with it - or an Emacs
mode in the Scite editor. At least I can use the File -> Revert to get
changes when I use Emacs for longer editing sessions. I've been bitten
once by the fact that Ctrl-S (or File -> Save) does not check whether
the file on disk has changed since the last time it was opened/saved by

Thanks for an outstanding piece of free software!


The information contained in this email transmission may contain proprietary and business 
sensitive information.  If you are not the intended recipient, you are hereby notified that 
any review, dissemination, distribution or duplication of this communication is strictly 
prohibited.  Unauthorized interception of this e-mail is a violation of law.  If you are not 
the intended recipient, please contact the sender by reply email and immediately destroy all 
copies of the original message.

Any technical data and/or information provided with or in this email may be subject to U.S. 
export controls law.  Export, diversion or disclosure contrary to U.S. law is prohibited.  
Such technical data or information is not to be exported from the U.S. or given to any foreign
person in the U.S. without prior written authorization of Elbit Systems of America and the 
appropriate U.S. Government agency.