Am 02.07.2010 02:11, schrieb Reimar Grabowski:
From your mail it is not clear which ld and as you used. I just took them from
the Android NDK, you too?
Unfortunately I currently have no time to play around with your code,
but I will as soon as I can.
Under linux I'm using self-built arm bin
Michael wrote:
> If 'sysutils' is somewhere included (I assume it is) it means that a
> different loadlibrary function is called.
Thanks for the response. Actually, I saved the assembly code generated
from both ways and compared them and realized the problem was with the
definition of HModule.
cl
02.07.2010 23:44, Alan Krause wrote:
I don't use lazarus, and am trying to automate the entire build and
release cycle for the different platforms.
You don't need to use it for every build. Just once to create the res
file with version information. If you include that res file into your
proje
Paul,
I don't use lazarus, and am trying to automate the entire build and release
cycle for the different platforms. Can you provide me with a sample that can
be compiled from the command line, or point me towards the appropriate
documentation?
Thanks much,
Alan
On Fri, Jul 2, 2010 at 8:34 AM,
02.07.2010 23:29, Alan Krause wrote:
On the Windows platform, version information is often included as a
resource which can be queried & displayed. Is there any way to include
this information in the 64-bit fpc compiled DLL?
Use Lazarus IDE for editing you dll project. You can set the version
I have recently ported over a DLL from Delphi to fpc, so we can offer the
DLL as a shared library on 32/64 bit linux, as well as 64-bit Windows.
On the Windows platform, version information is often included as a resource
which can be queried & displayed. Is there any way to include this
informati
On Fri, 2 Jul 2010, Seth Grover wrote:
Whoa... I discovered that simply adding "dynlibs" to the interface
uses clause of ssl_openssl_lib causes the crash to go away and
everything to work fine.
After further experimentation, if I put "dynlibs" in the uses clause
of ssl_openssl_lib prior to "C
Whoa... I discovered that simply adding "dynlibs" to the interface
uses clause of ssl_openssl_lib causes the crash to go away and
everything to work fine.
After further experimentation, if I put "dynlibs" in the uses clause
of ssl_openssl_lib prior to "Classes", it still crashes. If I add it
after
Greetings once again! I've run into a little bit of a strange problem
that I'm hoping someone here will be able to help me figure out.
I'm using, as I suspect some of you may be, the excellent synapse
project (http://ararat.cz/synapse). I have a simple 64-bit project
which consists only of:
==