[TRE-general] tre

[skaller]

On Wed, 2006-05-10 at 04:58 +0300, Ville Laurikari wrote:
> On Tue, May 09, 2006 at 03:05:46PM +1000, skaller wrote:
> > This is why in the first instance I tried to build TRE
> > from source *inside* Felix, in particular since it
> > alone has proper control over the target environment.
> > 
> > The build currently works 'out of the box' from
> > CMD.EXE command line in windows for win32. No need
> > for Cygwin or Mingw -- many Windows programmers have
> > only Microsoft tools available.
> 
> Can MSVC Developer Studio be assumed? 

MS provides free compilers (if you know where to
find them), but no IDE with them, just command line.

My system is built entirely from command line.
More precisely I use Python

	os.system(" .... ")

to invoke external tools, this is basically the same 
as ISO C system() function.

I happen to have VS2003 (XP) and VS2005 (XP64) so I can 
in theory build binaries for redistribution.

For XP, I can make MSI packages with VS2003. Compiling the library
should be easy -- the hard bit is configuring the switches
and figuring out which libraries are needed. Actually mingw
makes perfectly good win32 C libraries that MSVC++ can use,
just compile under Cygwin with

	-mnocygwin

I think. The problem then is to find the libs for i18n etc.
However I don't think any of this will work for win64.

For XP64 it is a nightmare with VS2005 because MSI is no longer.
Instead, they have assemblies, manifests, and some complex
mechanism that means you have to distribute a component --
library or application -- with all its non-system dependencies.
The C library isn't counted as a system library and so must
be redistributed.

So far I haven't figured out how all this works ;(
[Prefer working on Linux .. :]

If I can I'd be happy to provide an AMD64 binary.

Be warned that native code libraries are being phased out entirely
with .NET. It is possible to generate CLR bytecodes with VS2005
instead of native code -- exactly what this will do to libraries
like TRE I don't know.

>  TRE comes with a project file
> so you can build it from command line something like this: 
> 
>   msdev tre\tre.dsw /MAKE "ALL - RELEASE"

It should be possible to use the studio to create a Makefile.

> If anyone has built TRE for win64 I'd be glad to hear it. 

Me too!

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net