I made the windows port, the first example compiled and executed correctly. I am sending a patch so you can test it if i didn't break linux compatibility. Otherwise, I will look into deja-gnu testing, perhaps can compile it on windows. I will also add other beckend in the future (Sparc, PowerPC). I hope windows using Visual C++ will be soon officially supported :) About the problem I had with system and ltdl.c, it was resolved preaty easily by defining __WINDOWS__ globally in project. I also added a global macro for strtoll because the windows version is strtol (not strtoll). macro replaces strtoll with strtol and it compiles. I found really a lot of warnings in the project. Should I clean them? GCC probably doesn't throw them, so I don't know ... I don't even want to try to compile with VS8 which is even better at warnings ... Otherwise, I hope to use llvm (and of course also the port) for my project, baadengine (www.baadengine.org). llvm would serve as a script compiler (could be static or to bytecodes and JIT-ed at execution). I have already made the compiler (parsing, code extraction), all I need is to send it to LLVM to process it for me. So you can soon expect a new frontend for BSF scripts (Baadengine scripts format - java/C# like language, used for this project). Reegards, Žiga Osolin -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: llvm.patch URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20061104/aa5915d3/attachment.ksh>
> Otherwise, I will look into deja-gnu testing, perhaps can compile it on > windows. I willThe deja-gnu testing framework will most likely have to be rewritten to run on Windows. Its very unix specific. -Tanya> also add other beckend in the future (Sparc, PowerPC). I hope windows using > Visual C++ will be soon officially supported :) > > About the problem I had with system and ltdl.c, it was resolved preaty easily > by defining > __WINDOWS__ globally in project. I also added a global macro for strtoll > because the > windows version is strtol (not strtoll). macro replaces strtoll with strtol > and it compiles. > > I found really a lot of warnings in the project. Should I clean them? GCC > probably doesn't > throw them, so I don't know ... I don't even want to try to compile with VS8 > which is even better at warnings ... > > Otherwise, I hope to use llvm (and of course also the port) for my project, > baadengine (www.baadengine.org). llvm would > serve as a script compiler (could be static or to bytecodes and JIT-ed at > execution). I have already made the compiler > (parsing, code extraction), all I need is to send it to LLVM to process it > for me. So you can soon expect a new > frontend for BSF scripts (Baadengine scripts format - java/C# like language, > used for this project). > > Reegards, > �iga Osolin > >
On 11/4/06, Tanya M. Lattner <tonic at nondot.org> wrote:> > > Otherwise, I will look into deja-gnu testing, perhaps can compile it on > > windows. I will > > The deja-gnu testing framework will most likely have to be rewritten to > run on Windows. Its very unix specific. >How about building under MSVC 7.1 but using Cygwin for running deja-gnu? -Jey Kottalam