Hi,
for some reason I have to have a compiler creating binaries for FreeBSD
4 at hand.
Since all computers around here are on the way to FreeBSD 6 or 7 I have
to decide between having a seperate disk or partition or virtual machine
for FreeBSD 4 and setting up a build environment running on v6 an
On 20 Aug 2008, at 08:22, Werner Bochtler wrote:
This works fine for the commandline but if I try to add e.g.
-k"-install_name libTest.1.dylib" to my local configuration file
fpc.cfg
I get the following error message:
ld: unknown option: -install_name libTest.1.dylib
/usr/bin/libtool: inter
Hello,
Am 20.08.2008 um 15:37 schrieb T. Guilleminot:
For portability reason I would need to keep my shared libraries in the
same directory as the binary which need to call them.
As per http://courses.cs.vt.edu/~cs3304/FreePascal/doc/prog/
node13.html :
"This program can be compiled without a
Hello,
Am 20.08.2008 um 12:41 schrieb leledumbo:
After downloading the docs, I notice that there's a difference between
downloaded version and the one on the site. fpctoc in downloaded
version
doesn't have any link to FCL docs.
PS: Oh, God... The optimization options are still the old ones
Hi,
For portability reason I would need to keep my shared libraries in the
same directory as the binary which need to call them.
As per http://courses.cs.vt.edu/~cs3304/FreePascal/doc/prog/node13.html :
"This program can be compiled without any additional command-switches, and
should run just lik
Op woensdag 20-08-2008 om 03:44 uur [tijdzone -0700], schreef leledumbo:
> Is it possible? I usually use 2.3.1, but sometimes I need the stable version,
> too. I'd like to build everything from source as I'm doing a custom build
> (at least, not just 'make all').
Try it, and you'll see that it won
Is it possible? I usually use 2.3.1, but sometimes I need the stable version,
too. I'd like to build everything from source as I'm doing a custom build
(at least, not just 'make all').
--
View this message in context:
http://www.nabble.com/Compiling-FPC-2.2.2-with-2.3.1-tp19066885p19066885.html
After downloading the docs, I notice that there's a difference between
downloaded version and the one on the site. fpctoc in downloaded version
doesn't have any link to FCL docs.
PS: Oh, God... The optimization options are still the old ones! Is there any
links to those -OoXXX?
--
View this mess
>> Can anyone give me a hint how to set the 'soname'in FPC shared libraries
>> for LINUX?
>
> If -o doesn't work, nothing will.
-o does work but it changes the output name *and* the soname.
My intention is to generate e.g. a library libTest.so.0.1.0 with soname
libTest.so.0.
Using -o libTest.so
In our previous episode, Werner Bochtler said:
>
> Can anyone give me a hint how to set the 'soname'in FPC shared libraries
> for LINUX?
If -o doesn't work, nothing will.
> I have tried to pass "-soname libTest.so.0" via the k-switch to the
> linker but this doesn't seem to work.
-k is a stopg
Hi,
Can anyone give me a hint how to set the 'soname'in FPC shared libraries
for LINUX?
I have tried to pass "-soname libTest.so.0" via the k-switch to the
linker but this doesn't seem to work.
The ppas.sh file (see excerpt below) shows that the passed option
"-soname libTest.so.0" is overwritte
Jonas Maebe wrote:
>
> On 19 Aug 2008, at 12:55, Werner Bochtler wrote:
>
>> Can anyone give me a hint how to set the 'install_name',
>> 'compatibility_version' and 'current_version' in FPC shared
>> libraries for Mac OS X?
>
> In exactly the same way as for a C shared library: by passing the
12 matches
Mail list logo
