Koenraad Lelong wrote:
Koenraad Lelong wrote:
Jeff Pohlmeyer wrote:
...
...
Second question : are c-double types and fpc-double types compatible ?
This must be : c-float and fpc-double.
Sorry for that.
Koenraad.
___
fpc-pascal maillist - fpc-pascal@list
Koenraad Lelong wrote:
Koenraad Lelong wrote:
Jeff Pohlmeyer wrote:
...
I'm trying this and it seems to work, partly.
I wrote a clone in fpc of the temp-program, and encountered some strange
things.
The library successfully detects the interface, and one device (only one
connected at the time).
Nikolay Nikolov wrote:
Koenraad Lelong wrote:
Second question : are c-double types and fpc-double types compatible ?
I think so. Perhaps cfloat and cdouble should be added to the ctypes unit?
Already in the cvs.
___
fpc-pascal maillist - fpc-pascal@li
> Last question to Jeff Pohlmeyer : could you explain
> how you made that unit ?
Hello, Koenraad...
There is not really a one-size-fits-all solution to this,
but in general this is what I did for this particular case:
# be sure to clean up any leftovers first:
rm -f all.h all_inc.h all_mac.
Koenraad Lelong wrote:
Second question : are c-double types and fpc-double types compatible ?
I think so. Perhaps cfloat and cdouble should be added to the ctypes unit?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.o
Koenraad Lelong wrote:
Jeff Pohlmeyer wrote:
...
About the beer, it's pretty close.
1-wire devices are devices like termometers, AD-converters and other
devices that can be accessed over 1-wire (actually two : gnd).
And I would like to use these thermometer-devices with my Zaurus PDA to
measure t
Jeff Pohlmeyer wrote:
If you want to take a look, I've put it on
http://users.edpnet.be/~koenraad/www
Okay, try this...
In your ulinuxgnu300 directory, type:
make clean
make linux
ar -r libonewire.a *.o
ranlib libonewire.a
And then move the resulting "libonewire.a" file into
a directory
Jeff Pohlmeyer wrote:
If you want to take a look, I've put it on
http://users.edpnet.be/~koenraad/www
Okay, try this...
In your ulinuxgnu300 directory, type:
make clean
make linux
ar -r libonewire.a *.o
ranlib libonewire.a
And then move the resulting "libonewire.a" file into
a directory
> If you want to take a look, I've put it on
> http://users.edpnet.be/~koenraad/www
Okay, try this...
In your ulinuxgnu300 directory, type:
make clean
make linux
ar -r libonewire.a *.o
ranlib libonewire.a
And then move the resulting "libonewire.a" file into
a directory where the link
Jeff Pohlmeyer wrote:
I still don't understand what sort of c "package" you have
that generates a bunch of object files, but doesn't create
a shared library or static archive.
Does it have its own makefile or configure script?
Sometimes adding --enable-shared or --enable-static
to configure will
Am So, den 13.03.2005 schrieb Jeff Pohlmeyer um 00:03:
[..]
> > > Maybe I'm too used to using Delphi, where such things
> > > are hidden from the developper.
>
> > That's the nice part of Delphi.
>
> You are talking about searching the system for object
> files generated by another compiler and
I still don't understand what sort of c "package" you have
that generates a bunch of object files, but doesn't create
a shared library or static archive.
Does it have its own makefile or configure script?
Sometimes adding --enable-shared or --enable-static
to configure will tell it to build a li
> Let me explain more : the header file is used in at least
> five source-files, so compiling gives (at least) five .o
> files, but none with the name of the header-file.
>From the command line :
ar -r libDallas.a file1.o file2.o ...
and then, in your program:
{$LINKLIB Dallas}
- Jef
13 matches
Mail list logo
