Re: [Swig-devel] how to build swig on windows

[William S F. <ws...@fu...>]

Ivan

The Bison files are normally shipped with SWIG, so you can get them from
any release tarball. I compile the Windows distribution with Visual
Studio 8 and it contains the Ubuntu generated parser.c and parser.h, so
I don't understand how come you are having problems compiling these
files. Perhaps there is something new in svn head since 1.3.33 causing
problems or you have a different version of bison? swigwin-1.3.33 was
generated with bison-2.3 on Ubuntu Feisty. Try compiling
swigwin-1.3.33.zip as that should work.

William

Lucena, Ivan wrote:
> William,
> 
> I compiled the swig source from SVN trunk in VC71 (Microsoft Visual 
> Studio 2003). In order to do that I added those file generated on Ubuntu:
> 
> <swig>\Source\CParse\parser.c (*)
> <swig>\Source\CParse\parser.h (*)
> <swig>\Source\Include\swigconfig.h
> 
> It does compile and generate a swig.exe but the Yacc productions (*) are 
> not totally compatible with the windows environment, so if you try to 
> run swig with a csharp or python example it will give you compilation 
> errors on the wrappers. The best thing to do is to get a Windows 
> versions of Bison and run it manually before the build. I guess.
> 
> I am still working on it.
> 
> The off-site SWIG module is a Delphi module developed by S.
> Moratto. He provided my with a delphi.cxx module and also the VC71
> project. He is on this discussion list too.
> 
> I guess it would be interesting to have those *4 files* on a zip file
> for download. So that people can do a "SVN checkout" and then unzip the
> complement files over it.
> 
> <swig>\Source\CParse\parser.c (*)
> <swig>\Source\CParse\parser.h (*)
> <swig>\Source\Include\swigconfig.h
> <swig>\Source\Win\swig.vcproj
> 
> Best regards,
> 
> Ivan
> 
> 
> William S Fulton wrote:
>> Lucena, Ivan wrote:
>>> Hi William,
>>>
>>> Thanks for the tip. Sorry for my movie joke.
>>>
>>> I do have a Ubuntu under vmWare and I might use it as you said.
>>>
>>> I think I understood the point here. The process of building SWIG
>>> involve the use of UNIX tools normally unavailable in Windows, like m4,
>>> yacc, sed, awk, configure, autoheader or something else...
>>>
>>> I can see it on <swig>\Source\Include:
>>>
>>> /* ../swigconfig.h.  Generated from swigconfig.h.in by configure.  */
>>> /* ../swigconfig.h.in.  Generated from configure.in by autoheader.  */
>>>
>> Yes, some unix tools are required to generate swigconfig.h. You can of 
>> course generate this by hand and then use Visual C++ to compile it 
>> all, but then you need to figure out what needs doing.
>>
>>> But if I download the pre-build swigwin-1.3.33.zip I would expect to
>>> find those file already generated by whatever/whoever build the
>>> swig.exe. Nope.
>>>
>> The only thing different to swigwin-1.3.33.zip to the normal unix 
>> distribution, swig-1.3.33.tar.gz, is the addition of swig.exe.
>>
>>> And I suppose that swigwin-1.3.33.zip is not constantly updates with the
>>> SVN trunk either. Right?
>>>
>> Yup this is only released for releases. There is no equivalent to the 
>> swigwin package for in subversion, it is built from svn.
>>
>>> That is OK. I will get it working one way or another. BTW, I am
>>> interested in the latest fix to lua and I am also using another off-site
>>> SWIG module.
>>> >
>>> > http://www.swig.org/Doc1.3/Windows.html#Windows_swig_exe
>>> >
>>> > http://www.dabeaz.com/cgi-bin/wiki.pl?DeveloperInfo/GettingStarted
>>> >
>> These two links give you everything you need. Actually, if you use the 
>> Ubuntu route as per the wiki page, I'd be interested in your feedback 
>> as I'd like to know if I included all the packages that need 
>> installing in order to build the Windows executable. Is the off-site 
>> SWIG module for any freely available language or some custom language 
>> of your own?
>>
>> William
>>
>>
> 
> 
>