> yeah that technique requires far less stubs but it means that the coder has
> to manually call an init function.
>
> also how does your code respond if one of the entry points isn't found?
Myself I use
{$IFDEF DEBUG}
if getprocaddress(somefunc) = nil then write('somefunc getproc error');
{$EN
yeah that technique requires far less stubs but it means that the coder has
to manually call an init function.
also how does your code respond if one of the entry points isn't found?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Joost van
> der Sluis
On Tue, 2006-05-09 at 21:26 +0100, peter green wrote:
> > > What i'd like to see is compiler level support for loading
> > dynamic libraries
> > > and binding thier functions on demand.
> >
> > Like the database-base packages do? (example:
> > packages/base/ibase/ibase60dyn.pp)
> ok that unit reall
> > What i'd like to see is compiler level support for loading
> dynamic libraries
> > and binding thier functions on demand.
>
> Like the database-base packages do? (example:
> packages/base/ibase/ibase60dyn.pp)
ok that unit really confuses me, it seems to treat procedures declared
external as if
On Tue, 2006-05-09 at 20:31 +0100, peter green wrote:
> What i'd like to see is compiler level support for loading dynamic libraries
> and binding thier functions on demand.
Like the database-base packages do? (example:
packages/base/ibase/ibase60dyn.pp)
But here I've used wrappers. But it's not
What i'd like to see is compiler level support for loading dynamic libraries
and binding thier functions on demand.
this would mean a lot more flexibility. New features could be used without
breaking compatibility with older versions of the library. Version and
naming issues could be dealt with at
> But on several
> PCs I have 5 FreeBSD installtaions running from FreeBSD 5.5RC, 6.0
> Release, to 6.1RC in several Patchlevels.
All fairly new versions, except for 6.0. But you probably use -HEAD there
for the ports tree? The branch from the ports tree that you use is where the
difference is a
On 9 mei 2006, at 16:03, Luiz Americo wrote:
The bug 5098 was marked by Peter as not a bug because the file
handle would be opened inside a dll (another process), but the
examples where the bug is show does not uses another process or
dll. It simply implements a class in a separeted unit a
The bug 5098 was marked by Peter as not a bug because the file handle would be
opened inside a dll (another process), but the examples where the bug is show
does not uses another process or dll. It simply implements a class in a
separeted unit and then create a instance of this class inside anot
forwarded:
> --
> Two or three months ago I tested Lazarus on FreeBSD 6.0 RELEASE.
> After installing some missing libs (like pixbuf-devel, etc.) it
> compiled and run without any problems. Lazarus version was 0.9.12
> IIRC.
> --
> To my best knowledge, this naming depen
>
> On 9 mei 2006, at 11:21, Marco van de Voort wrote:
>
> > FreeBSD, when confronted with this says to use pkgconfig, and
> > doesn't want
> > to help out with a couple of symlinks to ease the situation. IOW
> > they don't
> > care about anything but GCC.
>
> This symlink/library practice o
On Tue, 9 May 2006, Felipe Monteiro de Carvalho wrote:
Hello,
There are some gtk 2 X11 bindings located at
lazarus/components/opengl/gtk2x11
I think we should add this to Free Pascal.
When I asked for this some months ago it was said that the bindings
were beta, but software that use TTra
Hello,
There are some gtk 2 X11 bindings located at lazarus/components/opengl/gtk2x11
I think we should add this to Free Pascal.
When I asked for this some months ago it was said that the bindings
were beta, but software that use TTrayIcon like the magnifier have
being using it for months now w
On 5/9/06, Mattias Gaertner <[EMAIL PROTECTED]> wrote:
I heard that the gtk1 libs under FreeBSD are libglib-12.so, libgdk-12.so and
libgtk-12.so.
But at the moment the linklib directive for FreeBSD defines
{$ifdef FreeBSD}
gtkdll='gtk12';
{$linklib gtk12}
without the '-'.
Can som
On 9 mei 2006, at 11:21, Marco van de Voort wrote:
FreeBSD, when confronted with this says to use pkgconfig, and
doesn't want
to help out with a couple of symlinks to ease the situation. IOW
they don't
care about anything but GCC.
This symlink/library practice on linux/unix is simply a me
> I heard that the gtk1 libs under FreeBSD are libglib-12.so, libgdk-12.so and
> libgtk-12.so.
> But at the moment the linklib directive for FreeBSD defines
> {$ifdef FreeBSD}
> gtkdll='gtk12';
> {$linklib gtk12}
> without the '-'.
>
> Can someone with FreeBSD please test if changi
I heard that the gtk1 libs under FreeBSD are libglib-12.so, libgdk-12.so and
libgtk-12.so.
But at the moment the linklib directive for FreeBSD defines
{$ifdef FreeBSD}
gtkdll='gtk12';
{$linklib gtk12}
without the '-'.
Can someone with FreeBSD please test if changing
packages/extra
17 matches
Mail list logo