Known issues for the first release (we won't fix these before release)
# Simple view renders badly.
# XML parsing is awful.
# Other things we inherited from BOINC and haven't fixed yet.
Immediately after release, our first task in the next release cycle
will be to switch to CMake.
Comments?
David Barnard
You mean Charlie's? That may be tricky, mixed with the async RPC mess...
> # Merge preference changes.
Do you think you can make it for the first release?
> Immediately after release, our first task in the next release cycle
> will be to switch to CMake.
Oh noes, work for me /o\
:)
I just successfully built the manager with CMake. Now synecd, syneccmd and
synecmgr all work.
I had to add clientlib, because it's required for the manager. What should we
call the DLL? The client uses it via LoadLibrary so filenames have to match.
Currently, every target is compiled in a separate directory:
build/api/boinc_api.lib
build/lib/boinc.lib
build/lib/syneccmd.exe
build/client/synecd.exe
build/clientlib/clientlib.lib
build/clientlib/clientlib.dll
build/clientgui/synecmgr.exe
But this means, for example, that you can't run synecmgr from the build
directory, because it won't find clientlib.dll.
To fix this I'd have to reorganize the scripts quite a bit: make a single
script, maybe split into files with the top-level script including them (literal
inclusion, like the C preprocessor). Currently there are independent scripts
that are called by the top-level script ("recursive make").
To clarify... I just successfully built it on *Windows* (generating a NMake
makefile). The Linux build was already working a few days ago :)
Mac still doesn't work, and will be a bit tricky, as I think CMake doesn't quite
support Objective-C (there are a few Obj-C and Obj-C++ files to compile).