Am Mittwoch 09 Dezember 2009 15:26:11 schrieb Graeme Geldenhuys:
> But clearly this language relationship is a very one-sided thing. We use
> their (C/C++) libraries, they don't use ours. :-(
Just look at the QT bindings. The LCL can't simply use QT, it has to use a
wrapper library that flattens
On Wed, 9 Dec 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt wrote:
I could not say it more concise as this, Marco wrapped it up nicely.
Like I said in a earlier reply, I don't want to add any more work to my
already long todo list.
I just thought if it was something quick and easy to
Michael Van Canneyt wrote:
>
> I could not say it more concise as this, Marco wrapped it up nicely.
Like I said in a earlier reply, I don't want to add any more work to my
already long todo list.
I just thought if it was something quick and easy to do, then it would be
nice to allow languages li
On 09 Dec 2009, at 15:22, Graeme Geldenhuys wrote:
Out of curiosity I tried, but I can't find any 'unstripped' .so
files on my
Linux system. So Midnight Commander doesn't show me anything, other
than
what architecture the .so file is.
A dynamic library cannot be completely stripped, becau
Marco van de Voort wrote:
>
> You see mangled names, exactly what you would see if you did this on a C++
> .so. IOW this dll is not flattened.
>
> Do this on a C dll to see the difference.
Out of curiosity I tried, but I can't find any 'unstripped' .so files on my
Linux system. So Midnight Comma
On Wed, 9 Dec 2009, Marco van de Voort wrote:
In our previous episode, Graeme Geldenhuys said:
2. Since FPGui is object oriented, it will be unusable unless you devise
a 'flat' API.
Is't there a way the FPC compiler can automatically flatten object oriented
code?
No.
As a test I crea
In our previous episode, Graeme Geldenhuys said:
> > 2. Since FPGui is object oriented, it will be unusable unless you devise
> >a 'flat' API.
>
> Is't there a way the FPC compiler can automatically flatten object oriented
> code?
No.
> As a test I created a new library project and included
Michael Van Canneyt wrote:
>
> 2. Since FPGui is object oriented, it will be unusable unless you devise
>a 'flat' API.
Is't there a way the FPC compiler can automatically flatten object oriented
code?
As a test I created a new library project and included the
fpgui_toolkit.pas unit which con
On 09 Dec 2009, at 14:30, Michael Van Canneyt wrote:
On Wed, 9 Dec 2009, Graeme Geldenhuys wrote:
Is it possible, or is there something special that needs to be done
to
create a library that could be used by other languages?
For example. I'm interested in created a library (.dll and .so) o
Michael Van Canneyt wrote:
>
> 1. Not without package support.
What exactly does that mean? In Lazarus I can go "File > New... > Library"
which is a package that compiles to a .so file under Linux.
> 2. Since FPGui is object oriented, it will be unusable unless you devise
>a 'flat' API.
Ah
On 09 Dec 2009, at 14:23, Graeme Geldenhuys wrote:
Is it possible, or is there something special that needs to be done to
create a library that could be used by other languages?
Just make sure that the exported routines
a) are declared as cdecl or stdcall (depending on platform requirements)
On Wed, 9 Dec 2009, Graeme Geldenhuys wrote:
Hi,
Is it possible, or is there something special that needs to be done to
create a library that could be used by other languages?
For example. I'm interested in created a library (.dll and .so) of fpGUI
Toolkit, so the library can be reused by ot
Hi,
Is it possible, or is there something special that needs to be done to
create a library that could be used by other languages?
For example. I'm interested in created a library (.dll and .so) of fpGUI
Toolkit, so the library can be reused by other fpGUI based applications
(reducing deployment
13 matches
Mail list logo