hello Jonas,
what do you think about using another fpc.cfg file (i.e. fpcxcode.cfg)
for iPhone compilation, rather than passing compiler configuration
through the command line?
i guess that the ideally, there would be no additional .cfg files, and
compiler should use common configuration.
But for
On 21 Mar 2009, at 10:38, dmitry boyarintsev wrote:
hat do you think about using another fpc.cfg file (i.e. fpcxcode.cfg)
for iPhone compilation, rather than passing compiler configuration
through the command line?
i guess that the ideally, there would be no additional .cfg files, and
compiler
On 21 Mar 2009, at 13:58, Jonas Maebe wrote:
On 21 Mar 2009, at 10:38, dmitry boyarintsev wrote:
Also, i'm not experienced in compiling fp-cross-compilers, but is it
possile to build ppcarm (for darwin) from svn trunk?
1) copy /Developer/FreePascalCompiler/iPhoneSnapshot-2.3.1-r12531/
Thanks for the comments.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
hello Jonas,
thanks for advancing with fpc for iPhone development.
i have a question: i'm using fpc trunk, so copmiled i386 units are not
located at /usr/local/lib/fpc/2.3.1/units/i386-darwin. Is there any
way to reconfigure the building script, so compiled units are taken
from the proper
Thanks!
i've also solved the error, by creating a symbolic link of
/usr/local/lib/fpc/2.3.1/units/i386-darwin to /Users/..release
path.../i386-darwin
dir...
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
On 20 Mar 2009, at 16:46, dmitry boyarintsev wrote:
i have a question: i'm using fpc trunk, so copmiled i386 units are not
located at /usr/local/lib/fpc/2.3.1/units/i386-darwin. Is there any
way to reconfigure the building script, so compiled units are taken
from the proper directory?
The
Hello,
As promised last week, I've released a small update to the FPC for
iPhone SDK 2.x. The changes since the previous release are:
* Mention that you need a certificate from Apple to run self-written
applications on an iPhone/iPod Touch
* Installation script mentions its location
