From: William S F. <ws...@fu...> - 2006-06-07 20:10:11
|
SWIG is no good for that. It could be though if someone wrote a new 'language' module to wrap C++ code with C++ via a flattened C interface. It has been talked about before. Then you'd compile the C code with cygwin's gcc to access the C++ .a file and you'd compile the C++ wrapper with VC++. This will work as the C interface exported by a dll is portable, ie not compiler specific. There are limitations to the approach, eg public member variables cannot be accessed as variables, instead go via public getters/setters. William Serethos wrote: > > I still don't know what this has to do with SWIG though. > > This is what I want to find out. While reading I guess SWIG is for all > some problems related to > using different languages with each other (talking in a simple way ..). > A solution for my problem > could be to make the .a library (which has been compiled with a > non-VC-compatible compiler) > compatible to VC. > So the question is, can I realize that with SWIG. > > > > Sohail Somani wrote: >>> -----Original Message----- >>> From: swi...@li... >>> [mailto:swi...@li...] On Behalf Of Serethos >>> >> >>> I would prefer to disclaim the bypass of using cygwin and a cross >>> compiler at all. A guy of the cygwin mailing >>> list indicated that the SWIG-Project could help me out of >>> this. It would >>> be a great help if somone could give >>> me a hint if this is possible. >>> >> Do you have access to the source of said simulator? If so, you could >> rebuild it using Visual C++... >> >> You might also want to put a DLL in between your library and the static >> library of the simulator. >> >> I still don't know what this has to do with SWIG though. >> >> > > > > _______________________________________________ > Swig-user mailing list > Swi...@li... > https://lists.sourceforge.net/lists/listinfo/swig-user > |