s in the
clang call..
can you point me in the right direction ?
like where is -T iphonesim processed ?
thanks
john
On Wednesday, June 16, 2021, 10:43:33 AM PDT, conlin664 via fpc-pascal
wrote:
Jonas,
thanks but I'm still a little stuck.I only do this kind of thing once every
ompilation aborted
make[3]: *** [ppc] Error 1
make[2]: *** [cycle] Error 2
make[1]: *** [compiler_cycle] Error 2
make: *** [build-stamp.x86_64-iphonesim] Error 2
On Wednesday, June 9, 2021, 11:50:08 AM PDT, Jonas Maebe via fpc-pascal
wrote:
On 09/06/2021 01:15, conlin664 via fpc-pasc
Guys,
I'm jumping up to the latest xcode 12.5to be able to develop on iOs 14.x
My trusty old FPC 3.0.5 worked just fine for iOs Target.
But the simulator is a different story...
Showing All Messages
ld: building for iOS/iOS Simulator, but linking in object file built for iOS
Simulator,
file
'/
Marc,
Hmmm. Okay, I just switched it to be stdcall
and had to slightly alter the name, but it compiled and ran.
So my example is now with "cpp" names, so my HelloC is now:
procedure HelloC; stdcall; external name '__Z6HelloCv';
vs
procedure HelloC; cdecl; external name '_Z6HelloCv';
both lin
THANKS GUYS.
This is now working. The 'fix' was to actually install fpc 3.0.4 on this
machine.
My trusty 2.4.4 still compiled just fine what I use it for here at my day
job.
But it seems 2.4.4 was not really pulling in the static reference.
{ $L ccode.o }
So for anyone else searching on this:
c
sven,
so I just tried, what I think you said:
procedure HelloC; cdecl; external name 'HelloC';
pcode.pas(19,1) Error: Undefined symbol: _HelloC
sorry for complaining about windows, but i feel like this is more difficult
on windows.
All of the FPC examples, seem to run without this extra '_' b
ok. I backed up to a simple version.
how I declare the C routine must be the problem,
with nothing,
procedure HelloC; cdecl; external;
I think it's trying to static link it, and gets an
pcode.pas(19,1) Error: Undefined symbol: _HelloC
with anything else
procedure HelloC; cdecl; ex
Thanks for the suggestions..
I'm pretty sure now, that the problem is that I'm thinking that the C code
is being statically linked,
but right now the compiler is going for dynamic.
[ I've been comparing the size of the .exe ]
I also compiled with -va and note:
[0.388] Number of unresolved extern
I've done research, but am just missing something.
my .pas code links just fine, but doesn't RUN.
( first writeln never appears )
If I remove the external call to C code, then the writeln works as normal.
Problem:
I have c code, which I'm compiling on a WIN32 machine ( yes the horror )
using GC
