>I have been trying to adapt the Unix CMake files for the Windows port,<br><br>nice!!<br><br>If I am correct, when you generate sources with VMMaker you get something like this:<br><br>\-src<br> \-plugins <- external plugins<br>
\-pluginA<br>
\-pluginB<br> \-vm <- interpreter, gc, etc.<br> \intplugins <- internal plugings. Inside vm dir makes sense because <br> they'll be statically linked to the VM.<br>
\-pluginC<br> \-pluginD<br><br>This is all generated from Slang. You may have some other part of some plugins in Cross/plugins if they have code directly written in C.<br><br><br>Regards,<br>
Javier.<br><br><br><div class="gmail_quote">On Tue, Apr 13, 2010 at 12:58 PM, Geoffroy Couprie <span dir="ltr"><<a href="mailto:geo.couprie@gmail.com">geo.couprie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Hello,<br>
<br>
I have been trying to adapt the Unix CMake files for the Windows port,<br>
but I have difficulties understanding the sources layout. I understand<br>
at least the difference between internal and external plugins, but<br>
what is in vm/intplugins? It seems that CMake looks for sources in a<br>
lot of directories, and that some of them are not used anymore. I have<br>
these directory layouts:<br>
platforms<br>
\-Cross<br>
\-plugins<br>
\-pluginA<br>
\-pluginB<br>
\-vm<br>
\-specificplatform<br>
\-plugins<br>
\-pluginA<br>
\-pluginB<br>
\-vm<br>
<br>
And for the generated sources directory:<br>
src<br>
\-pluginA<br>
\-pluginB<br>
\-vm<br>
<br>
Is that the definitive sources layout?<br>
<br>
Also, if you're interested in using CMake for Windows, should I<br>
assemble Unix and Windows instructions in the same files?<br>
<br>
Best regards,<br>
<font color="#888888"><br>
Geoffroy Couprie<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Javier Pimás<br>Ciudad de Buenos Aires<br>