After much googling, still can't find any clue.
Synapse claims it supports cross platform.
I check the difference between hello world and tcpclient1 program.
hello world:
8000:Searching file /usr/lib/fpc/2.5.1/units/arm-linux/rtl/prt0.o...
found
tcpclient1:
8000:Searching file
/usr/lib/
On 6 November 2010 19:39, Felipe Monteiro de Carvalho wrote:
>
> Did you try making executables for Android? It is possible to run
> native executables from Java.
I'm very interested in this too. My next toy is going to be a Android
based tablet (mostly for ebook reading), but I would like to deve
On 6 November 2010 18:29, yu ping wrote:
> I want to set up Lazarus as FPC Editor and Debuger.
> But Lazarus installation is too big,How to install a minimal size of
> Lazarus?
In that case, simply use MSEide instead. It's much smaller and faster.
It's a 1.8MB (Windows) or 2.0MB (Linux) download
On Sat, Nov 6, 2010 at 8:46 PM, Reimar Grabowski wrote:
> I don't know of any way running native executables from Java on this
> platform. It is definitly not officially supported.
Here is a tutorial:
http://gimite.net/en/index.php?Run%20native%20executable%20in%20Android%20App
It just uses st
On Sat, 6 Nov 2010 18:39:53 +0100
Felipe Monteiro de Carvalho wrote:
> Did you try making executables for Android? It is possible to run
> native executables from Java.
It is not my code but I know a bit about Android.
I don't know of any way running native executables from Java on this platform.
On 06.11.2010 18:11, Marco van de Voort wrote:
In our previous episode, Sven Barth said:
AFAIK PE DLLs are always relocatable while it's not true for ELF SOs. So,
whenever you need to create it, always pass -fPIC to ALL used units and
their dependencies.
PE images themselves aren't relocatabl
Hello,
Did you try making executables for Android? It is possible to run
native executables from Java.
That would be somewhat better then running the code from a .so
Also a tutorial about how to create the cross-compiler and set
everything up would be excelent ...
>From your zip file it seams t
In our previous episode, Sven Barth said:
> >
> > AFAIK PE DLLs are always relocatable while it's not true for ELF SOs. So,
> > whenever you need to create it, always pass -fPIC to ALL used units and
> > their dependencies.
>
> PE images themselves aren't relocatable. All addresses are relative to
I want to set up Lazarus as FPC Editor and Debuger.
But Lazarus installation is too big,How to install a minimal size of
Lazarus?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
W dniu 06.11.2010 08:25, leledumbo pisze:
AFAIK PE DLLs are always relocatable while it's not true for ELF SOs. So,
whenever you need to create it, always pass -fPIC to ALL used units and
their dependencies.
So where else can I put this switch to fix lNet compiler errors?
___
06.11.2010 22:16, ik wrote:
why not something like this:
TAClass = class
private
FField : class integer;
end;
"var" and "class var" starts new sections in the class declaration.
Therefore you can define several class fields or instance fields after them.
For example
TAClass = class
private
On Sat, Nov 6, 2010 at 17:13, Paul Ishenin wrote:
> 06.11.2010 21:39, ik wrote:
>
>> But why class variables and not class fields ?
>>
> What is the difference?
>
> "var" is already a reserved word. reserving a word "field" will cause more
> problems than using an already reserved word.
>
why n
06.11.2010 21:39, ik wrote:
But why class variables and not class fields ?
What is the difference?
"var" is already a reserved word. reserving a word "field" will cause
more problems than using an already reserved word.
Best regards,
Paul Ishenin.
On 06.11.2010 15:39, ik wrote:
But why class variables and not class fields ?
As I personally think about normal class fields as "variables per class
instance", I see no difference between calling something "class field"
or "class variable".
If it is the "var" keyword you are stumbling on,
On 06.11.2010 08:25, leledumbo wrote:
AFAIK PE DLLs are always relocatable while it's not true for ELF SOs. So,
whenever you need to create it, always pass -fPIC to ALL used units and
their dependencies.
PE images themselves aren't relocatable. All addresses are relative to
the defined base a
But why class variables and not class fields ?
Ido
LINESIP websites:
http://www.linesip.com
http://www.linesip.co.il
On Sat, Nov 6, 2010 at 09:26, leledumbo wrote:
>
> > I think both are basically identical, but the work of the first one is
> > much more clear. I had never used them, but I
> I think both are basically identical, but the work of the first one is
> much more clear. I had never used them, but I think the above code is
> right, do not ?
Yes. Usually we need this when creating a thread pool, so we know how many
threads have been created.
--
View this message in conte
AFAIK PE DLLs are always relocatable while it's not true for ELF SOs. So,
whenever you need to create it, always pass -fPIC to ALL used units and
their dependencies.
--
View this message in context:
http://free-pascal-general.1045716.n5.nabble.com/Problems-with-relocation-errors-tp3252196p325285
18 matches
Mail list logo
