Menu
▾
▴
SF.net SVN: frontierkernel: [1326] Frontier/branches/Conversant
|
From: <set...@us...> - 2006-04-22 21:06:56
|
Revision: 1326 Author: sethdill Date: 2006-04-22 14:06:49 -0700 (Sat, 22 Apr 2006) ViewCVS: http://svn.sourceforge.net/frontierkernel/?rev=1326&view=rev Log Message: ----------- Merged r1297:1323 from trunk into Conversant branch. Final batch. Modified Paths: -------------- Frontier/branches/Conversant/FrontierSDK/Toolkits/AppletToolkit/Headers/appleticons.h Frontier/branches/Conversant/README.txt Modified: Frontier/branches/Conversant/FrontierSDK/Toolkits/AppletToolkit/Headers/appleticons.h =================================================================== --- Frontier/branches/Conversant/FrontierSDK/Toolkits/AppletToolkit/Headers/appleticons.h 2006-04-22 21:01:48 UTC (rev 1325) +++ Frontier/branches/Conversant/FrontierSDK/Toolkits/AppletToolkit/Headers/appleticons.h 2006-04-22 21:06:49 UTC (rev 1326) @@ -9,13 +9,13 @@ -#define atNone 0x0 -#define atVerticalCenter 0x1 -#define atTop 0x2 -#define atBottom 0x3 -#define atHorizontalCenter 0x4 -#define atLeft 0x8 -#define atRight 0xC +#define atNone 0x00 +#define atVerticalCenter 0x01 +#define atTop 0x02 +#define atBottom 0x03 +#define atHorizontalCenter 0x04 +#define atLeft 0x08 +#define atRight 0x0C extern unsigned short ttLabel [8]; Modified: Frontier/branches/Conversant/README.txt =================================================================== --- Frontier/branches/Conversant/README.txt 2006-04-22 21:01:48 UTC (rev 1325) +++ Frontier/branches/Conversant/README.txt 2006-04-22 21:06:49 UTC (rev 1326) @@ -1,18 +1,95 @@ -*** UserLand Frontier(tm) -- Version 10.0 Open Source Release +*** UserLand Frontier(tm) -- Version 10.1 Open Source Release *** -Last updated 02 Jan 2005 by Terry Teague +Last updated 22 Apr 2006 by Andre Radke Since the original v10.0a1 Open Source release of Frontier, additional work has been done to allow the building of Frontier using other development environments. The following sections describe these environments. -*** Supported Development Environments +A. Apple Xcode Tools for Mac OS X +================================= + +Build directory : build_XCode -A. Metrowerks CodeWarrior Pro for Mac or Windows +Getting Started with Xcode v1.2 or v1.5 or v2.0 +----------------------------------------------- + +1. Open the Frontier.xcode project in Xcode. + +2. Click the Build button. + +Getting Started with Xcode v2.1 and higher +------------------------------------------ + +1. Open the FrontierFat.xcodeproj project in Xcode. + +2. Click the Build button. + +Notes +----- + +Both the Frontier.xcode and the FrontierFat.xcodeproj projects offer a +development and a deployment build style. + +In the FrontierFat.xcodeproj +project, the development build style will compile for the native +architecture only, but the deployment build style will compile a +Universal Binary of Frontier which will run on both PPC and Intel Macs. + + +B. Microsoft Visual Studio .NET 2005 +==================================== + +Build directory: build_VC2k5 + +Getting Started: +---------------- + +1. Open the Frontier.sln solution file in Visual Studio. + +2. Select the Configuration Manager from the Build menu and switch +the Active Solution Configuration to Debug. Click the Close button. + +3. Select Build Solution from the Build menu. + + +C. Microsoft Visual Studio .NET 2003 +==================================== + +Build directory: build_VC2k3 + +Getting Started: +---------------- + +1. Open the Frontier.sln solution file in Visual Studio. + +2. Select the Configuration Manager from the Build menu and switch +the Active Solution Configuration to Debug. Click the Close button. + +3. Select Build Solution from the Build menu. + + +D. Microsoft Visual Studio C++ 6.0 for Windows +============================================== + +Build directory : build_VC6 + +Getting Started +--------------- + +1. Open the Frontier.dsp project in MS Visual Studio. + +2. Choose a build configuration from the Project menu. It is a good idea +to start with the Debug build configuration. + +3. Build. + + +E. Metrowerks CodeWarrior Pro for Mac or Windows ================================================ -CVS module, build directory : build_CWPro8 +Build directory : build_CWPro8 Building the Frontier kernel currently requires Metrowerks CodeWarrior Pro 8 for Mac or Windows with the 8.3 updates. Other versions might @@ -40,77 +117,26 @@ Notes ----- -When you open the Frontier.mcp project file on Windows or on classic Mac -OS, CodeWarrior will complain that the access path +When you open the Frontier.mcp project file on Windows, CodeWarrior will +complain that the access path {System}Library/CFM Support/StubLibraries cannot be found. This means that you will not be able to build the Mac -OS X version on those platforms, but it does not affect the versions for -Windows and classic Mac OS. +OS X version on that platforms, but it does not affect the versions for +Windows. -When you build the Frontier PPC or Frontier PPC Debug targets, expect -CodeWarrior to report a single link warning about the errno variable -being defined in OTXTILib and MSL_ALL_PPC.Lib (or MSL_ALL_PPC_D.Lib). -You can safely ignore this warning. - When you build the Frontier Win or Frontier Win Debug target, expect CodeWarrior to report about 240 compiler warnings, mostly about redeclared identifiers in Microsoft header files, some missing function prototypes, and some unused variables. You can ignore these warnings. -B. Microsoft Visual Studio C++ for Windows +F. GNU Tools (initially for Mac OS X only) ========================================== -CVS module, build directory : build_VC6 +Build directory : build_GNU -Building the Frontier kernel currently requires Microsoft Visual Studio -C++ v6. Other versions might work, too, but have not been tested. - -Getting Started ---------------- - -1. Open the Frontier.dsp project in MS Visual Studio. - -2. Build. - -Notes ------ - -Needs more accurate build instructions. - - -C. Apple Xcode Tools for Mac OS X -================================= - -CVS module, build directory : build_XCode - -Building the Frontier kernel currently requires Xcode v1.2 or v1.5. -Other versions might work, too, but have not been tested. - -Getting Started ---------------- - -1. Open the Frontier.xcode project in Xcode. - -2. Click the Build button. - -Notes ------ - -The support for Xcode is preliminary, and currently builds a Debug -(Development build style) version by default. - -When you build, expect Xcode to report a couple of compiler warnings. -You can ignore these warnings. - - -D. GNU Tools (initially for Mac OS X only) -========================================== - -CVS module, build directory : build_GNU - Building the Frontier kernel currently requires the Mac OS X Developer Tools to be installed on Mac OS X. Older tools using Project Builder, or newer tools using Xcode should work, using 'gcc' v3.3. Other versions of @@ -143,7 +169,7 @@ Support for building the Windows version using Cygwin/MinGW or other GNU based development environments on Windows systems, and support for building the Windows -version using WINE on non-Windows systems, is being developed. +version using WINE on non-Windows systems, may be added in the future. *** Reporting Problems This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
