On Mon, Mar 30, 2009 at 8:04 PM, David Cournapeau <cournape at gmail.com> wrote: > On Tue, Mar 31, 2009 at 2:37 AM, Alexander Neundorf > <alex.neundorf at kitware.com> wrote: ... >> Not sure I understand. >> Having a project which builds (shared) libraries and executables which >> use them (and which maybe have to be executed later on during the >> build) is no problem for CMake, also with the VisualStudio projects. >> >From what I remember when I wrote the CMake files for python it was >> quite straight forward. > > I think Christian meant that since on windows, those are built with > visual studio project files, but everywhere else, it is built with > distutils, you can't use a common system without first converting > everything to cmake for all the other platforms. Can you please explain ? What is "those" ? > Also, when converting a project from one build system to another, > doing the 80 % takes 20 % in my experience. Getting it working took me like 2 days, if that's 20% it's not too bad ;-) > The most time consuming > part is all small the details on not so common platforms. Yes. Alex
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4