As told by the objectivepascal web site,
I download and installed the template
http://dl.dropbox.com/u/28343282/ObjP/Xcode_Templates.html
however, when I compiled an IOS project, it stuck at the unit not found
iPhoneAll.pas
I tried to give it a full path by changing it to:
uses
iPhoneAll i
On 09 Nov 2012, at 02:30, Noah Silva wrote:
haha I see. It seemed very easy at the time, though. The binaries
were
just there, so I linked them. The reason for doing it that was was
just
that the installer/FAQ mentioned using the "Unix tools" option in the
installer, but the "installer"
Hi Jonas,
haha I see. It seemed very easy at the time, though. The binaries were
just there, so I linked them. The reason for doing it that was was just
that the installer/FAQ mentioned using the "Unix tools" option in the
installer, but the "installer" is different now the App Store and has no
On 01 Nov 2012, at 05:38, Noah Silva wrote:
> 2012/8/16 Jonas Maebe
>
>> FPC works with the assembler and linker of Xcode 2.x up to and
>> including the latest Xcode 4.x, but with Xcode 4.3 and later you have to
>> but with Xcode 4.3 and later you have to install them separately
>
> Really? I
Hi,
>but with Xcode 4.3 and later you have to install them separately
Really? I just had to link them from the appropriate folder in the XCode
application bundle (to the global binary folder). Perhaps this is because
I used to have 3.x on the same machine?
Thank you,
Noah Silva
2012/8/16 J
On 29 Oct 2012, at 15:18, Tomas Hajny wrote:
Out of curiosity, I tried the link to "Phil Hess' templates" at the
bottom
of the download page on FPC main site (your first link) and noticed
that
it leads to nowhere now. Probably something to be fixed before 2.6.2
at
latest (but preferably a
On Mon, October 29, 2012 10:43, Jonas Maebe wrote:
> On 29 Oct 2012, at 05:15, ĺ°ĺ ´ äšäş wrote:
.
.
> You don't have to make any symlinks. You have to follow the
> instructions on the download page:
> * at the top of http://www.freepascal.org/down/i386/macosx-netherlands.var
> * at the bottom
On 29 Oct 2012, at 05:15, 印場 乃亜 wrote:
Currently, a beginner user who just wants to use Lazarus has to:
a. Download a multi gigabyte XCode install just for a few MB of
binaries.
And the SDKs.
b. Know what binaries the FPC installer is looking for, where they
will be, and where the instal
Hi,
Even for me (and I have installed FPC / Lazarus on Mac like 100 times now),
things are mysterious sometimes.
I upgraded my 10.7 laptop to 10.8, and the existing lazarus/ FPC, and XCode
continued to work fine, despite reading various places that upon upgrading, the
Unix Tools would be delet
Franz wrote on Wed, 15 Aug 2012:
Since version 4.3.3 Xcode is installed only as application in folder
applications. Some folders are apparent in content of application
but distinguishing in substance with folder developer.
Will or until when will free pascal developed for earlier version of
Can somebody explain Xcode-installtion?
Last version of free pascal is 2.6 and working with Xcode 3.2.6.
Meanwhile last Xcode version is 4.4.1. Version 4.1 was installed with new
folder "Developer" and folder of version 3.2.6 was redefined to
"Developer-(null)".
Since version 4.3.3 Xcode is inst
0 +0200
>From: Jonas Maebe
>Subject: Re: [fpc-pascal] Xcode access to fpc documentation
>To: FPC-Pascal users discussions
>Message-ID: <963ac7c8-1313-46ac-a81f-f2ecbfb7d...@elis.ugent.be>
>Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
>
>On 27 Jan
On 27 Jan 2009, at 00:55, Ken G. Brown wrote:
Is there a way to add the fpc documentation so that Xcode help can
access it like the docsets?
Not that I know.
In the MacOS fpc 2.2.2 download, in the MainUnit.pas of the FPC-C-C+
+CarbonApplication template for new projects, there is a typo
Is there a way to add the fpc documentation so that Xcode help can access it
like the docsets?
In the MacOS fpc 2.2.2 download, in the MainUnit.pas of the
FPC-C-C++CarbonApplication template for new projects, there is a typo causing
it to not compile.
The ) after $endif should be }.
{$if not d
14 matches
Mail list logo
