Native use of FPC+Lazarus on MacOS X is fine.
Even native use of FPC+Lazarus on Mac OS X cross compile to IOS is fine
using the specialized Lazarus + FPC 2.7.1 + the packakge provided by
www.pas4mobile.com
I have deployed an IOS app on my Ipod touch without problem (of course,
you need to
On 23/06/13 20:56, Florian Klämpfl wrote:
So they support now native development on MacOS X as well?
No, all development is still ONLY done under Windows. You cross compile
to OS X and iOS. You also remote debug to OS X and iOS.
I still think forcing a Windows licence for somebody that wants
On 06/21/2013 07:43 PM, Sven Barth wrote:
Just to clear up the names: UnicodeString is *not* the code page aware
string type (although they share the metadata record). It is a
dynamic length 2 byte string. The code page aware string type is
AnsiString.
Thanks for making this clear.
On 06/21/2013 06:23 PM, Dennis Poon wrote:
Please do share your experience with BeagleBone
I don't do anything myself on that behalf right now, butt I'll let you
know when I hear success or fail stories from my friend Karlheinz.
especially on how to write OSless FPC applications on it.
On 06/21/2013 06:39 PM, Florian Klämpfl wrote:
Does it have an fpu which supports exception handling?
I am not aware of this special issue.
The CPU is a AM 335x by TI. A quick search of the nearly 5000 page Chip
handbook did not reveal anything on that behalf to me.
-Michael
Michael Schnell schrieb:
Could you give us a list of the different - legacy and to be supported
- string types we might be seeing including their official names to
make the discussion less ambiguous.
This should be clear since a long time. I e.g. remember your strange
(Delphi incompatible)
On 06/24/2013 12:43 PM, Hans-Peter Diettrich wrote:
This should be clear since a long time.
Sorry, but e.g. I don't know the official names of the Delphi 7
compatible String and the Delphi XE compatible String in fpc/Lazarus.
I suppose in DXE the Delphi 7 compatible String is not available
anyone knows *all* the different ways that function names may be mangled
(for the linker)?
I asked because this is sometime the only info returned by gdb (if there
is no debug info). And it could be useful to parse it.
It used to be Unit_class_$__function$...
In our previous episode, Michael Schnell said:
I do now that that the Delphi 7 compatible String in fpc sometimes has
been called ANSIString, while Lazarus funnily stores UTF8 in the type
ANSIString, even in spite of the naming.
You can funnily store utf8 in type ansistring under Delphi 7
On 06/24/2013 03:11 PM, Marco van de Voort wrote:
You can funnily store utf8 in type ansistring under Delphi 7 too.
Yep. But D7 does not rely on some string to be encoded in UTF8 (but in
the ANSI table the System configuration defines), while the LCL API
wants to see the strings in UTF8 code.
On 24 Jun 2013, at 15:07, martin wrote:
anyone knows *all* the different ways that function names may be
mangled (for the linker)?
Probably only svn blame/praise combined with checking out old
versions of compiler/symdef.pas does.
I asked because this is sometime the only info returned
On 24/06/13 14:25, Jonas Maebe wrote:
You should not try to parse the mangled name, because FPC's name
mangling is a one-way process at this time (and always has been until
now). If the mangled name's length gets close to 250 characters, the
end will be replaced by a CRC of the name
Michael Schnell schrieb:
On 06/24/2013 12:43 PM, Hans-Peter Diettrich wrote:
I e.g. remember your strange (Delphi incompatible) opinions about
RawByteString and encodings in a startup discussion.
Yep. As I did not have DTX to try it, I only read what I could find in
the internet and
On 24-6-2013 17:13, Michael Schnell wrote:
On 06/24/2013 04:44 PM, Hans-Peter Diettrich wrote:
Not in Delphi. For binary data TBytes has been added.
Which (AFAIK) is not reference counting can't do + and thus much
less versatile.
It is also highly controversial since XE4:
For example a
On 24-6-2013 17:15, Michael Schnell wrote:
Karlheinz said on the Phone that the boots in some 10 seconds to
the command line when using the original Angstrom Distribution and at
least 20 seconds when using Debian.
-Michael
___
fpc-devel
Thanks for your info.
For information, my Raspberry Pi running the ArchLinux boots within 16
seconds to the command line using an old class 4 SD Card.
If running Raspbian, it boots to the graphical UI in 30 seconds using a
new Class 10 SD Card.
Does have a stable stock supply?
Dennis
On Mon, Jun 24, 2013 at 11:25 AM, Dennis Poon den...@avidsoft.com.hkwrote:
**
Does have a stable stock supply?
Note this response I saw to a question about the BeagleBoard/BeagleBone:
Are we talking the design or the board? We will not guarantee continued
supply of any version of the
On 24.06.2013 15:40, martin wrote:
On 24/06/13 14:25, Jonas Maebe wrote:
You should not try to parse the mangled name, because FPC's name
mangling is a one-way process at this time (and always has been until
now). If the mangled name's length gets close to 250 characters, the
end will be
On 24.06.2013 11:36, Michael Schnell wrote:
On 06/21/2013 07:43 PM, Sven Barth wrote:
Just to clear up the names: UnicodeString is *not* the code page aware
string type (although they share the metadata record). It is a
dynamic length 2 byte string. The code page aware string type is
On 24.06.2013 16:44, Hans-Peter Diettrich wrote:
I hope, now I understand that the type RawByteString ( = String
($) ) means codesize = 1 Byte, never to be auto-converted to any
differently encoded String type variable.
No. Even if I would like such an encoding, too, Delphi doesn't
Am 24.06.2013 01:39, schrieb Graeme Geldenhuys:
On 23/06/13 20:56, Florian Klämpfl wrote:
So they support now native development on MacOS X as well?
No, all development is still ONLY done under Windows. You cross compile
to OS X and iOS. You also remote debug to OS X and iOS.
This is my
Sven Barth schrieb:
On 24.06.2013 16:44, Hans-Peter Diettrich wrote:
I hope, now I understand that the type RawByteString ( = String
($) ) means codesize = 1 Byte, never to be auto-converted to any
differently encoded String type variable.
No. Even if I would like such an encoding, too,
22 matches
Mail list logo
