On Sun, Dec 22, 2013 at 11:52:04PM +0100, Hans-Peter Diettrich wrote:
Keeping UTF8 on Windows makes a majority platform seem only half supported.
Not good either. Worse, it is Delphi incompatible.
You favor a special FPC and Lazarus for Windows, in addition to the
UTF-8 version for all
On Sat, Dec 21, 2013 at 05:11:29PM +, Mark Morgan Lloyd wrote:
I know that this is not a supported combination, but I've just been
trying to build trunk Lazarus (r43576) with trunk FPC (r26258) to see if
I can work around a couple of recently-fixed issues. FPC trunk builds
clean, and
On Mon, Dec 16, 2013 at 08:58:52AM +0100, Michael Van Canneyt wrote:
equivalent.
FWIW: the octal format of specifying numbers is relatively new and IIRC
only
available in FPC mode...
'relatively new' is relative.
I think octal notation has been available in FPC since many years.
Am 23.12.2013 12:23, schrieb Marco van de Voort:
On Mon, Dec 16, 2013 at 08:58:52AM +0100, Michael Van Canneyt wrote:
equivalent.
FWIW: the octal format of specifying numbers is relatively new and IIRC
only
available in FPC mode...
'relatively new' is relative.
I think octal notation
Juha Manninen schrieb:
However using a new Unicode-Delphi would cause
many problems because all VCL functions and classes, including
TStringList, expect UTF-16 string. When using UTF8String, the compiler
converts between encodings all the time.
Then you can give your favorite string type a
On Mon, Dec 23, 2013 at 1:58 PM, Hans-Peter Diettrich
drdiettri...@aol.com wrote:
Then you can give your favorite string type a unique name, and set it to
whatever is best in your favorite environment.
The favorite string type in this case would be UTF8String. It already
has a name. Please see
If I knew how to create the ubuntu packages, I would certainly do this.
Every time I need to install Lazarus on Windows I envy the ease of
installation.
--
Atenciosamente,
Alexsander da Rosa
--
___
Lazarus mailing list
Marco van de Voort wrote:
On Sat, Dec 21, 2013 at 05:11:29PM +, Mark Morgan Lloyd wrote:
I know that this is not a supported combination, but I've just been
trying to build trunk Lazarus (r43576) with trunk FPC (r26258) to see if
I can work around a couple of recently-fixed issues. FPC
Can anyone give me any ideas on how to access the data in the Project
Application dialogue ? Specifically the Version Number. I would like to
include the Version Number in both my About box as well as the Title Bar
of the main form but I have been unable to figure out how to access the
data
On 12/23/13, Hew Lines hewli...@shaw.ca wrote:
Can anyone give me any ideas on how to access the data in the Project
Application dialogue ? Specifically the Version Number. I would like to
include the Version Number in both my About box as well as the Title Bar
of the main form but I have
FILES needed:
fpc-2.6.2.i386-linux.tar
lazarus-1.0.14-0.tar.gz
fpc-src_2.6.2-0_i386.deb
Sources:
dpkg -i fpc-src_2.6.2-0_i386.deb
FPC:
tar -xvf fpc-2.6.2.i386-linux.tar
cd fpc-2.6.2.i386-linux/
./install.sh
Lazarus:
apt-get install libc6-dev-i386
apt-get install libX11-dev:i386
apt-get install
I think we're talking about the compiled application's version number.
On 12/23/2013 10:18 AM, Bart wrote:
On 12/23/13, Hew Lines hewli...@shaw.ca wrote:
Can anyone give me any ideas on how to access the data in the Project
Application dialogue ? Specifically the Version Number. I would
You can get the debs from sourceforge, or simply follow:
http://wiki.lazarus.freepascal.org/Lazarus_release_version_for_Ubuntu
It will come up in your package manager, much easier than windows installer
:)
--
View this message in context:
Am 2013-12-23 11:32, schrieb Marco van de Voort:
So I would say UTF16, and maybe, if there is demand, some can get utf8 :-)
The question is:
Should FPC and LCL use a fixed encoding for all platforms
or should the encoding be adapted for each WidgetSet/OS?
If it should be the same for all
On Mon, Dec 23, 2013 at 8:38 AM, Marco van de Voort mar...@stack.nl wrote:
On Sun, Dec 22, 2013 at 05:06:27PM -0200, Marcos Douglas wrote:
FPC 2.7.x can compile the windows unit in unicode (UTF16) mode. Most
system and
sysutils file related routines are already unicode (UTF16 with
Thanks Bart but that's not quite what I'm looking for. I'm looking for
the version number of the compiled application. It is set in the Version
Info panel of the Project Options dialogue box and auto-incremented with
every build. I know that I can do it manually but am trying to see if I
can
Are you sure it works? This wiki never worked for me.
2013/12/23 leledumbo leledumbo_c...@yahoo.co.id
You can get the debs from sourceforge, or simply follow:
http://wiki.lazarus.freepascal.org/Lazarus_release_version_for_Ubuntu
It will come up in your package manager, much easier than
Mark Morgan Lloyd wrote:
I know that this is not a supported combination, but I've just been
trying to build trunk Lazarus (r43576) with trunk FPC (r26258) to see if
I can work around a couple of recently-fixed issues. FPC trunk builds
clean, and Lazarus (default configuration) builds with FPC
I have used vinfo like described here:
Topic: Get and use the Build Number within your program
http://forum.lazarus.freepascal.org/index.php?topic=12435.0
And, this vinfo inspired rework might also help:
Topic: Accessing build info and compiler info in Source
On 23/12/2013 20:13, Mark Morgan Lloyd wrote:
Apologies for reformatting the message to conform to the usual
bottom-posting convention.
Hew Lines wrote:
On 2013-12-23 9:18 AM, Bart wrote:
On 12/23/13, Hew Lines hewli...@shaw.ca wrote:
I'm looking for
the version number of the compiled
Many thanks Anthony. Looks like exactly what I was looking for.
Hew
On 2013-12-23 11:01 AM, Anthony Tekatch wrote:
I have used vinfo like described here:
Topic: Get and use the Build Number within your program
http://forum.lazarus.freepascal.org/index.php?topic=12435.0
And, this vinfo
On 23/12/2013 20:16, Reinier Olislagers wrote:
On 23/12/2013 20:13, Mark Morgan Lloyd wrote:
Apologies for reformatting the message to conform to the usual
bottom-posting convention.
Hew Lines wrote:
On 2013-12-23 9:18 AM, Bart wrote:
On 12/23/13, Hew Lines hewli...@shaw.ca wrote:
I'm
On 2013-12-23 11:13 AM, Mark Morgan Lloyd wrote:
Apologies for reformatting the message to conform to the usual
bottom-posting convention.
Hew Lines wrote:
On 2013-12-23 9:18 AM, Bart wrote:
On 12/23/13, Hew Lines hewli...@shaw.ca wrote:
Can anyone give me any ideas on how to access the
Apologies for reformatting the message to conform to the usual
bottom-posting convention.
Hew Lines wrote:
On 2013-12-23 9:18 AM, Bart wrote:
On 12/23/13, Hew Lines hewli...@shaw.ca wrote:
Can anyone give me any ideas on how to access the data in the Project
Application dialogue ?
On 2013-12-23 11:18 AM, Reinier Olislagers wrote:
On 23/12/2013 20:16, Reinier Olislagers wrote:
On 23/12/2013 20:13, Mark Morgan Lloyd wrote:
Apologies for reformatting the message to conform to the usual
bottom-posting convention.
Hew Lines wrote:
On 2013-12-23 9:18 AM, Bart wrote:
On
On Mon, Dec 23, 2013 at 06:52:21PM +0100, J?rgen Hestermann wrote:
Am 2013-12-23 11:32, schrieb Marco van de Voort:
So I would say UTF16, and maybe, if there is demand, some can get utf8 :-)
The question is:
Should FPC and LCL use a fixed encoding for all platforms
or should the encoding
Marco van de Voort schrieb:
On Mon, Dec 23, 2013 at 06:52:21PM +0100, J?rgen Hestermann wrote:
Am 2013-12-23 11:32, schrieb Marco van de Voort:
So I would say UTF16, and maybe, if there is demand, some can get utf8 :-)
The question is:
Should FPC and LCL use a fixed encoding for all
27 matches
Mail list logo
