Pascal Viandier wrote:
<snip> > > I am working on that to give you a clear example of what happens. I > made a > simple test program using a module that contains the {$L } directive > and > gp > worked perfectly, even recompiling the c source when necessary. But > with > the > real life application it fails repeatedly. I am trying to find the > pattern > and will let you know. >
I found what is going on: I specify --object-destination-path=obj/dbg to gp. This option - as mentioned in a previous post - is not passed to gpc but I found that it is passed gcc so the gpc objects are in the gpi directory and the ones from gcc in obj/dbg. So the C objects are correctly compiled but not retrieved by gpc unless I put --object-path=obj/dbg option to gp.
I think this is a consequence of the fact that gp ignores the --object-destination-path option when it calls gpc. I will try to solve this one, if you agree.
But the gpc manual says:
--unit-destination-path Path where to create object and GPI files of Pascal units. --no-unit-destination-path Create object and GPI files of Pascal units in the current directory (default). --object-destination-path Path where to create additional object files (e.g. of C files, not Pascal units). --no-object-destination-path Create additional object files (e.g. of C files, not Pascal units) in the current directory (default).
Regards,
Adriaan van Os