E. Wing wrote:
Hi, sorry for the delay, but I just sacrificed my weekend trying to
get caught up on CMake things.
Thanks!
So all the issues are fuzzy. But here's what I remember:
....
We also have the Framework building support issues. Last time, we
spoke of this, we were having problems with versioning schemes. There
is .so, .dylib, framework, where .so conflicted with .dylib. I just
checked, and it does not appear to be fixed. We also ended up talking
about install_name, rpath, and now @rpath.
There were also other minor things with frameworks such as symlinks
being creating to nothing and unnecessary directories being created.
Another issue not explicitly discussed by me, but has been mentioned
in other contexts is installing to /usr instead of /usr/local. I
haven't checked in awhile, but last time I remember, the installer
package for CMake installs to /usr instead of /usr/local. This really
needs to change if it hasn't already been fixed.
Eric, if you could try 2.4.8 RC 4 and see what is missing that would
help a lot. I am not planning to fix or develop much more for 2.4.8.
Any new stuff or major changes will go in 2.6. So, 2.4.8 will not have
the ability to create frameworks. 2.4.8 is for fixing regressions and
bugs of 2.4.7 and not filling in missing features or working out long
standing issues. The problem with adding new stuff is that for each new
thing we add, it is sure to bring 2 more bugs... :)
So, please just bug fixes for 2.4.8. The general rules are:
- Does something not work in 2.4.8 that worked in 2.4.7
- Is there something that worked in 2.4.6- 2.4.0 that is broken in
2.4.7
- Is there something that is just a simple bug in 2.4.7, and
advertised feature that does not work.
Most everything else belongs in 2.6.0.
> That's all I can remember on Mac issues for the moment. But on a
> general CMake issue, I just submitted a whole bunch of Find*.cmake
> modules for inclusion.
> http://www.cmake.org/Bug/view.php?id=6139
>
Eric, the bug tracker is a real pain to handle module contributions.
This is why I setup the module maintainers. Would you like to become a
module maintainer?
http://www.cmake.org/Wiki/CMake:Module_Maintainers
You would get CVS access to the Modules directory in CMake, and you
would not have to wait for me to get around to extracting your modules
from the bug tracker.
Thanks
-Bill
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
