Bill Hoffman wrote:
Joshua Jensen wrote:
Well, now that I know what it is, I'll just turn off the
MACOSX_BUNDLE flag for the time being. I'll watch CVS for a fix.
It is broken for all targets in CVS at the moment for some reason
I would recommend not using cvs...
Unfortunately, there are
Joshua Jensen wrote:
Well, now that I know what it is, I'll just turn off the MACOSX_BUNDLE
flag for the time being. I'll watch CVS for a fix.
It is broken for all targets in CVS at the moment for some reason I
would recommend not using cvs...
As a follow up question... why is that step
Bill Hoffman wrote:
Joshua Jensen wrote:
ersion of CMake are you using? Also, I don't think CMake has
anything to do with the clean target, it is managed by Xcode itself.
It does seems that this is currently broken in CVS, I am looking into
the issue. I have to figure out some way of testing
Joshua Jensen wrote:
ersion of CMake are you using? Also, I don't think CMake has
anything to do with the clean target, it is managed by Xcode itself.
I always forget the important stuff. I'm using latest CVS and the
latest version of Xcode.
It does seems that this is currently broken in
Bill Hoffman wrote:
Joshua Jensen wrote:
Upon using CMake with Xcode and instructing CMake to generate
application bundles, I've run into the following issues:
* When I make a change to a static library, the executable doesn't
relink. I have to rm it from the application bundle myself. Upon
Joshua Jensen wrote:
Upon using CMake with Xcode and instructing CMake to generate
application bundles, I've run into the following issues:
* When I make a change to a static library, the executable doesn't
relink. I have to rm it from the application bundle myself. Upon
digging through the
Upon using CMake with Xcode and instructing CMake to generate
application bundles, I've run into the following issues:
* When I make a change to a static library, the executable doesn't
relink. I have to rm it from the application bundle myself. Upon
digging through the (very verbose) build
