Re: Lua libraries

[jim@...]

one comment - Compiling Lua into a DLL in Visual C++ is easy... and I've 
never minded the lack of support for a Visual C++ project which can often 
have screwed up path information embedded in it from the host computer
that created it.  

However, relying on unix make file system for core functionality is bad
because then it becomes a nightmare to get things running in VC++.

Regards,
Jim



----- Original Message ----- 
From: "Nick Trout" <Nick.Trout@warthog.co.uk>
To: "Multiple recipients of list" <lua-l@tecgraf.puc-rio.br>
Sent: Thursday, January 31, 2002 10:38 AM
Subject: RE: Lua libraries


| > Hence "tries" to be platform independent. The supplied makefile can be
| > used under Windows with either Cygwin or Mingwin tools, so it's pretty
| > close to platform independent. I admit that it doesn't work in the VC
| > world.
| 
| I would suggest is most Windoze users dont have cygwin or mingwin installed
| and would be a lot more comfortable using their chosen compiler than
| adopting this solution. You still end up having to build the whole thing
| yourself on whatever compiler is available with whatever build system you
| have. Anyway I think your point was that you want a simple way to add
| libraries in the code, not that there are cross platform build issues.
| 
| > > > become a job for an enhanced dist., with enhanced libs &c.
| > >
| > > Probably not as it would need updating regularly to 
| > incorporate fixes etc.
| > 
| > Was that an agreement or a disagreement? "Updating regularly" 
| > sounds like
| > just the thing for an enhanced dist, and just what you want 
| > to avoid for
| > the standard dist.
| 
| I'm agreeing with your disagreement. It shouldnt be in the standard dist. as
| it will be regularly altered. There should be an easy (multiple makefile
| IMHO) way to build Lua quickly out of the box and potentially another system
| which is more complex.
| 
| Regards,
| Nick
| 
| 
|