From: Stefano M. <ste...@gm...> - 2008-07-03 08:11:56
|
William, I developed the module using both Visual Studio (2005) C++ and mingw so I have working windows and unix like compile environments. I followed all the requirements in http://www.swig.org/Doc1.3/Extending.html#Extending_prerequisites. I checked the diff command and it is available in my mingw environment so I will proceed with the building of the diff package. I will assure to have unix style LF in the code. Today I'm going to modify the makefiles in order to compile with FPC. Maybe it will be sufficient to ./configure --with-delphi-compiler=fpc or something similar. I ran the test suites only on few cases (two c++ and two c) but I would like to put the module online in order to find some help to finish the test suites. Yesterday I tried to send the docs to the list but it is to large > 40k and the list doesn't accept .zip files. BTW my SF account is smoratto Stefano On Thu, Jul 3, 2008 at 12:09 AM, William S Fulton <ws...@fu...> wrote: > Stefano Moratto wrote: >> >> Dear SWIG's community, >> >> I've developed a functional delphi module that >> implements all the swig functions except for director. >> The module compiles all the examples that can be found in the CSharp >> example's folder and I tested some testsuits (cpp_basic, bloody_hell, >> enums ). >> >> I would like this effort will be included in the standard SWIG because >> * I think the DELPHI community needs this tools; >> * I'm a developer in the GDAL project and I done a GDAL's >> version for delphi using SWIG but I can not include it in the standard >> GDAL distros >> while the Delphi module is not included in SWIG. >> >> How can I produce a patch to be sent to you? I developed starting from >> swigwin-1.35 sources. >> > > Stefano > > I think the best way to submit a patch is to send it to SF. Some people send > patches inline in an email, but usually the lines get broken up, then the > patch program can't patch properly. The patch will probably apply cleanly to > svn head even if you send the patch diff'd to 1.3.35. A unix/cygwin line > ending diff will be preferable. Please send any initial documentation you > have to the list too. > > We're always interested in new modules and Pascal would be a good one to add > to the list of supported languages. However, we are concerned about the > number of language modules that have been submitted and then not brought up > to scratch. It sounds like you have some basics working which is great. If > you havn't yet read the prerequisites for acceptance, please take a look at > http://www.swig.org/Doc1.3/Extending.html#Extending_prerequisites. > > We're an open source project and like to support other open source > languages, eg the C# module is designed to work with Mono as well as MS's > C#. Similary for Delphi, I'd hope that it works with free pascal. Free > Pascal 2.2.0 looks a doddle to install (under Debian/Ubuntu anyway). I'd be > quite happy to test it out if you havn't yet tried it out. It'll probably be > a lot easier to configure for the test-suite than using Windows unless you > are using cygwin or mingw's gcc. Ultimately, easily running the entire > test-suite error free is what is needed to maintain a language module. > > William > > -- Dr.Eng. Stefano Moratto |