Op Mon, 17 Jul 2006, schreef Jonas Maebe:
On 17 Jul 2006, at 14:03, Daniël Mantione wrote:
There's nothing C-specific about libraries, nor about the *config
scripts. At
most it would be linker-specific.
There is, those scripts mainly exist because a C compiler cannot
On 17 Jul 2006, at 14:57, Daniël Mantione wrote:
But if the new version has additional (or different) dependencies
or library
names, everything will remain fine with the script (as e.g. with
the FreeBSD
problem which started this discussion).
That is exactly what Marco's code solves, in
On Mon, Jul 17, 2006 at 02:35:41PM +0200, Micha Nelissen wrote:
Marco van de Voort wrote:
On Mon, Jul 17, 2006 at 01:56:38PM +0200, Micha Nelissen wrote:
the library name correctly according to that distro's packaging rules)
then all dependent software is automatically recompiled for the
Op Mon, 17 Jul 2006, schreef Jonas Maebe:
On 17 Jul 2006, at 14:57, Daniël Mantione wrote:
But if the new version has additional (or different) dependencies or
library
names, everything will remain fine with the script (as e.g. with the
FreeBSD
problem which started this
On 17 Jul 2006, at 16:01, Daniël Mantione wrote:
As I said, you do not have to parse that unless you have an
internal linker.
And even then you only have to parse linker options for the
platforms you
support. Also, depending on which gtk you link against on Mac OS X
you may
need to link
Op Mon, 17 Jul 2006, schreef Jonas Maebe:
Above you said that the compiler is the wrong location?
The compiler is from a software engineering point of view the wrong
location to call gtk-config and clones. However, it is the compiler's
task to pass the libraries a unit needs to the linker.
Jonas Maebe wrote:
On 17 Jul 2006, at 16:01, Daniël Mantione wrote:
We should design a system that does solve world hunger. I'm serious about
that: if we want to be a more professional tool than C, we should not
copy
the defficiencies. Makefiles are one of them, Autohell is another, and
On Monday 17 July 2006 15:03, Micha Nelissen wrote:
No these are separate things. The C compiler vendors do not provide a
common platform resulting in a differing mess that has to be held
together with scripts.
Of course they don't. Unlike some other languages where such things are
Vinzent Hoefler wrote:
Of course they don't. Unlike some other languages where such things are
standardized quite clearly, (most) consistency, dependency and linking
issues are beyond the scope of the official C-standard.
I'm not talking about the C language, but the vendors, the C library
On Mon, Jul 17, 2006 at 04:37:07PM +0200, Jonas Maebe wrote:
So, in order to support this, we would need to write a hack when a
{$linklink gtk} occurs and write gtk-config specific code. For a
different
library we would need a different hack.
Of course not. You should never change a
On 17 Jul 2006, at 22:36, Marco van de Voort wrote:
Of course not. You should never change a {$linklib magicstring} into
some command. The exact command(s) to be executed would have to be
embedded in the unit with a compiler directive (and probably, just
like library name, be ifdef'd per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings to the Fpc-Devel list:
I recently moved from Linux to FreeBSD as my primary work environment.
My development system of choice is FreePascal. I installed FPC-2.0.2
from the official FreePascal distribution tar ball, and all
Hi Bob and welcome to the world of crap.
Seriously and honestly, the FreeBSD porters made a big bad pile of crap
when they some years ago decided to name gtk-12 and others as gtk12.
Then they added to this pile of crap by renaming it back sometime after
6.0 release.
Long story short, it's not
Hi,
I've got a question about COM programming in FPC. In the docs
(http://www.freepascal.org/docs-html/ref/refsu20.html) I've found:
Variants and interfaces
Remark: Dispatch interface support for variants is currently broken in the
compiler.
Is it still true? Why when I try to compile this
Hello,
i want to ask about current gdb support on fpc state and its futture plans.
I tried to work with gdbpasw with program compiled with fpc106 and noticed
that some gdb funtionalities does not work on it. For example: xbreak,
watch. Then i tried them it was said that breakpoits are set, but
101 - 115 of 115 matches
Mail list logo
