can PB create LINUX shared objects or MacOSX dylibs?

Rozek · Post by **Rozek** » Tue Jun 17, 2008 11:01 am

Hello!

The question comes up from time to time in this forum - and sometimes the answer is not a complete "no", although there is never an explanation of how a "yes" could look like...

Thus: is it possible to create .so files for Linux or .dylib files for MacOSX in a similar way as one can create .dll files for Windows?

One could then implement functions using PB and make them available to other languages and environments.

Thanks in advance for any hint!

Kind regards,

Andreas Rozek

Foz · Post by **Foz** » Tue Jun 17, 2008 11:08 am

You did check the Compiler Options screen where you select the type of executable didn't you?

Rozek · Post by **Rozek** » Tue Jun 17, 2008 11:15 am

oops,

I was so fixed to looking into the forum first that I forgot to experiment with PB under MacOS X first...

Thanks for the hint and "mea culpa".

Sorry for bothering you!

Foz · Post by **Foz** » Tue Jun 17, 2008 11:16 am

Don't worry, it happens to the best of us

Rozek · Post by **Rozek** » Thu Dec 04, 2008 3:01 pm

Hello again!

Today, after several other projects I found some time to test building dynamically loadable libraries under Mac OS X.

However, I failed - here are my results

- the current "official" version produces a shared object, however, this library does not contain the symbol I tried to export
- the current "beta 4" simply emits a "linker error"
- "beta 5" complains about a missing "_main" symbol

Does anybody have any idea how I can build (the equivalent of) DLLs under Mac OS X (and, later, Linux)?

Thanks in advance for any help!

Rozek · Post by **Rozek** » Thu Dec 04, 2008 3:56 pm

Hmm, strange...

By "playing around" with the creation of "shared objects" under Mac OS X (Version 4.20) I found out:

- the given function names are never exported
- instead, PB exports the following symbols
- PS#, _ClearLoop# and _Procedure# with # = 0,2,4, ...
- _EndProcedure# with # = 0,1,2,3...

Let "n" be the number of functions to be exported, then

- the first series stops at 2*(n-1)
- the second series stops at 2*(n-1)+1

This looks really strange - does anybody have an explanation?

Trond · Post by **Trond** » Thu Dec 04, 2008 7:09 pm

I have, i have! Look at me! Look at me!

What I remember (to be confirmed by Fred):
Actually, it's broken for OS X at the moment. For Linux it should work.

Rozek · Post by **Rozek** » Fri Dec 05, 2008 7:21 am

oops,

that's bad - is there any information when it will work (again)?

Post by **Fred** » Fri Dec 05, 2008 2:22 pm

Trond is right, dylib on OS X doesn't work for now. It's planned for 4.40.

Rozek · Post by **Rozek** » Sat Dec 06, 2008 8:51 am

Thanks for the response!

Hmmm, this means that it will take a while...we are currently within the beta process of 4.30.

Kind regards,

Andreas Rozek

Niffo · Post by **Niffo** » Wed Jan 28, 2009 5:35 pm

Hello,

Please Fred, can you tell us what is really non-functional in Mac Version of PB :
- the generation (compilation) of dynlibs by PB
- the use of dynlibs (made in C for example) from PB ?
- both ?

Regards

Trond · Post by **Trond** » Wed Jan 28, 2009 7:32 pm

It's probably only the generation, anything else would be stupid.

Post by **Fred** » Sat Jan 31, 2009 6:41 pm

Yes, it's only the generation from PB code.

Niffo · Post by **Niffo** » Mon Feb 02, 2009 10:40 am

Thank you very much Fred for your answer