[Alephmodular-devel] Re: XCode 2.1
Status: Pre-Alpha
Brought to you by:
brefin
|
From: Br'fin <br...@ma...> - 2005-06-07 16:52:17
|
Working with AlephModular
Tag .pbjproj with XCODE-2_0
Open AlephModular.pbproj in XCcode 2.1
It prompts me to make a copy to be updated to an .xcodeproj.
I click 'Upgrade a copy'
It prompte me for where to save.
I select same name and directory. AlephModular.xcodeproj
Project file opens.
Project file still has:
the PB Compatible target
the XCode compatible target
no other new targets
(All sub files of project were copied over as well, notably the
project.pbxproj.in file I use for autoconf purposes in AM)
Notable changes:
Comments have been added to sections
All references are now followed by a comment specifying what is
being
referenced
All file references now have their expanded isa information
included in
their defining line (Translation: A file's base set of
information is
now all on one line)
CFlags specifiers are no longer a single quoted list, but an
array with one
quoted element per specified flag. This applies to
OTHER_CFLAGS
WARNING_CFLAGS
GCC_PREPROCESSOR_DEFINITIONS
OTHER_CPLUSPLUSFLAGS
(it does not apply to OTHER_REZFLAGS though)
Working in XCode:
Most elements that used to be in Info on the project file are now
specifally in the build target settings with the general
exception
of base target architecture.
Currently sticking with 'Current' May try 10.4 (universal)
if needed
Removing PB Compatible target
AM had this target so while the native XCode target was the
default,
additions of files could be added to the PB Compatible
target and
then merged into the PB-2_0 version of the project file.
With the changes to the file format, this is no longer
possible, so
we may as well remove it for simplicity. For A1 I
recommend moving
to an XCode native target and removing the PB
compatible one.
XCode now puts built files into a Configuration directory within
the build
directory. So you will need to move support files into the
new location,
for instance, maps and such at AM/A1 complain about if they
don't find.
This should be settable, I can't seem to locate it.
All of the version stuff delegated by configure.ac is either getting
outside the
bounds I can configure it in XCode (for instance, extra c-flags)
or wasn't
present in the project file for native targets (moved to
external file
Info-AlephModular.plist, specifically things like 0.4.0.CVS as an
application version.)
As such configuring the XCode project file for AM will be removed from
configure.ac. Which does make my life easier when adding files
to XCode.
AM is now compiling and running. However I want to normalize some
settings as
compared with a freshly created project and try and locate where the
option of a
universal build is even if I can't actually test the thing. :)
-Jeremy Parsons
http://alephmodular.sourceforge.net/
|