Re: [Beremiz-devel] How can I see full gcc command calls at project build console?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Beremiz-devel] How can I see full gcc command calls at project build console?

Beremiz-Devel mailing list

>> Good day, colleagues!
>>
>> I invent some ideas with Beremis, for example: place runtime on TI
>> am335x linux boards, like penguin or beagle-bone.
>> Now, I created target named "linux-armhf", forked from "Linux".
>> Difference is only on compiler name.
> You don't have to "fork" Linux target for this. You can just set right
> compiler (like arm-non-linux-gnueabihf-gcc), linker, CFLAGS and
> LDFLAGS in target properties.
> Your custom target properties will be saved in your project.

May be, but I did it in try to link whole project.so staticly... And in future fix $(cc) as arm-linux-gnueabihf-

>> And then I faced with problem
>> with "mjsousa/modbus" extention. Runtime on target system can not
>> find libmb.so (compiled obliviously for armhf too). But more
>> correctry will be to link extention libraries staticly, because of
>> we transfer only MD5**.so file thrue PYRO, isn't it?
> You can put compiled libmb.so on the target and transfering only
> project so will not be a problem anymore.

Unfortunately, placing libmb.so in some places over runtime with no sucess: near md5.so, dir higher or at Modbus dir like on desktop-linux.
Always seen message:
PLCobject : OFF LOG :NewPLC (806accc1ad47f269c68e43d944c16f5b)
working_dir/806accc1ad47f269c68e43d944c16f5b.so
PLCobject : Traceback (most recent call last):
  File "/opt/runtime/runtime/PLCObject.py", line 143, in LoadPLC
    self._PLClibraryHandle = dlopen(self._GetLibFileName())
OSError: libmb.so: cannot open shared object file: No such file or directory

> Or you can link the library staticaly using proper LDFLAGS in target properties.

Ok, I'll try it. But it will be some support if I see existed flags... That's my question about.

>> To findout how
>> it complet I need to see full detailed build log, may be at
>> "console" panel of beremiz. Is it possible? Or may be there is some
>> another way?
> If you we get build error, you will see complete build log in "console".

Yea, and got wish to compire with success build.




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Beremiz-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/beremiz-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Beremiz-devel] How can I see full gcc command calls at project build console?

Beremiz-Devel mailing list
On 17-06-01 16:50, [hidden email] wrote:

>
> >> Good day, colleagues!
> >>
> >> I invent some ideas with Beremis, for example: place runtime on TI
> >> am335x linux boards, like penguin or beagle-bone.
> >> Now, I created target named "linux-armhf", forked from "Linux".
> >> Difference is only on compiler name.
> > You don't have to "fork" Linux target for this. You can just set right
> > compiler (like arm-non-linux-gnueabihf-gcc), linker, CFLAGS and
> > LDFLAGS in target properties.
> > Your custom target properties will be saved in your project.
>
> May be, but I did it in try to link whole project.so staticly... And in future fix $(cc) as arm-linux-gnueabihf-
And you don't need to fork to target to link whole project.so
staticly. You just need right LDFLAGS.


> >> And then I faced with problem
> >> with "mjsousa/modbus" extention. Runtime on target system can not
> >> find libmb.so (compiled obliviously for armhf too). But more
> >> correctry will be to link extention libraries staticly, because of
> >> we transfer only MD5**.so file thrue PYRO, isn't it?
> > You can put compiled libmb.so on the target and transfering only
> > project so will not be a problem anymore.
>
> Unfortunately, placing libmb.so in some places over runtime with no sucess: near md5.so, dir higher or at Modbus dir like on desktop-linux.
> Always seen message:
> PLCobject : OFF LOG :NewPLC (806accc1ad47f269c68e43d944c16f5b)
> working_dir/806accc1ad47f269c68e43d944c16f5b.so
> PLCobject : Traceback (most recent call last):
>   File "/opt/runtime/runtime/PLCObject.py", line 143, in LoadPLC
>     self._PLClibraryHandle = dlopen(self._GetLibFileName())
> OSError: libmb.so: cannot open shared object file: No such file or directory
You have to place shared library to directory where dynamic loader can
find it.

The list of directories you can get by running following command:

ld --verbose | grep SEARCH_DIR | tr -s ' ;' \\012


> > Or you can link the library staticaly using proper LDFLAGS in target properties.
>
> Ok, I'll try it. But it will be some support if I see existed flags... That's my question about.

> >> To findout how
> >> it complet I need to see full detailed build log, may be at
> >> "console" panel of beremiz. Is it possible? Or may be there is some
> >> another way?
> > If you we get build error, you will see complete build log in "console".
>
> Yea, and got wish to compire with success build.



--
Best regards,
Andrey Skvortsov

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Beremiz-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/beremiz-devel

signature.asc (849 bytes) Download Attachment
Loading...