Re: [Eros-users] eros win_ros mingw_cross help

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Daniel Stonier
Date:  
To: Alexander Pérez Ruiz, eros-users
Subject: Re: [Eros-users] eros win_ros mingw_cross help
Hi Alex,

Not sure if you ran into it, but just found a bug in my mingw_cross
update that caused it to bomb when compiling log4cxx (forgot to copy
across patches). It's fixed now.

Cheers,
Daniel.

2011/5/18 Daniel Stonier <>:
> Oh, thanks for the heads up about the upgraded versions Alex. More info below:
>
> 2011/5/18 Alexander Pérez Ruiz <>:
>> Gday Daniel:
>>
>> I was absent for some weeks but now I am trying to create some nodes for
>> Windows.
>>
>> I have tried to follow the new guide to install the eros package in order to
>> compile my nodes but I have found some libraries like apr and the apr_util
>> have changed recently.
>>
>> Your script is looking for the apr_1.4.2 but it doesn't exist and the
>> current available version is the 1.4.4 and the available version of the
>> apr_util library is the 1.3.11 instead of the 1.3.10.
>
> Ok, I've changed the URLs to point to the archived 1.4.2 and 1.3.10
> packages for now.
>
> In addition, I'd created some build scripts so you can install
> everything when you make eros' mingw cross package, i.e. no need for
> toolchain bridge packages with mingw anymore). I had this in trunk
> though, but I just merged it into the diamondback tag. So if you svn
> update, a simple
>
> rm -rf /opt/mingw
> roscd mingw_cross
> make
> make links
>
> Should install mingw, compile gcc, apr, apr-util, log4cxx, boost and
> qt and then create symlinks to the mingw binaries in /usr/local/bin.
>
> Let me know how that goes.
>
>> I downloaded the latest versions of these libraries and I have compiled them
>> successfully but when I am trying to compile the log4cxx library I get the
>> following error:
>>
>> filewatchdog.cpp: In member function 'void
>> log4cxx::helpers::FileWatchdog::start()':
>> filewatchdog.cpp:90:24: error: invalid conversion from 'void*
>> (*)(apr_thread_t*, void*)' to 'void* (*)(apr_thread_t*, void*)'
>> filewatchdog.cpp:90:24: error:   initializing argument 1 of 'void
>> log4cxx::helpers::Thread::run(void* (*)(apr_thread_t*, void*), void*)'
>>
>> I don't know what it means or what the solution is. :S
>
> I fixed this a couple of weeks ago and posted an issue/patch to
> log4cxx (https://issues.apache.org/jira/browse/LOGCXX-382). I did this
> in trunk too thoush, so I just merged the trunk version of
> eros_log4cxx back to diamondback as well, so it should work now.
> However, if you just install mingw_cross from here on in, you
> shouldn't need eros_log4cxx for mingw anymore.
>
>> I was wondering if you have a new version of the rosbag migration to
>> mingw_cross? I am blocked because the rosbag did not compile correctly when
>> I tried to run rosprotect --preclean --minimal command.
>
> With mingw, just do a rosprotect --preclean --comms
>
> Then build individual packages around that. The --minimal flag is a
> way off for mingw and is used for cross compiling full arm systems.
>
> I had a look at porting rosbag last week, but there's an awful lot of
> linux termios code in there. I cant see anyone wanting to rosbag on
> windows for now (we're only currently interested in
> monitoring/debugging/simple apps atm). In the meantime I've ticketed a
> request to remove the rosbagmigration dependency from xxx_msgs
> packages (it's using python code anyway, so it doesn't need a compile
> time dependency). Strictly speaking though, that may not be considered
> a good approach as the manifests are used to indicate more than
> compile time dependencies (bit of a weakness in the current build
> system).
>
>> I need to compile a node to use in windows and the trick to remove
>> rosbagmigration dependency from the messages is not working. My nodes need
>> the sensor_msgs and nav_msgs packages.
>
> Did you remove the rosbagmigration dependency from manifest.xml's in
> geometry_msg, sensor_msg *and* nav_msg? I just did that here and it
> did work. I might add a patch in eros diamondback tag to handle that
> transparently when someone is cross compiling so you don't have to
> manually do it. As I implied above, it doesn't have any ill side
> effects that I'm aware of.
>
>> I would appreciate so much if you could help me with these problems.
>>
>> Best regards,
>>
>> Alexander.
>
> Cheers,
> Daniel.
>




--
Phone : +82-10-5400-3296 (010-5400-3296)
Home: http://snorriheim.dnsdojo.com/
Yujin Robot: http://www.yujinrobot.com/
Embedded Ros : http://www.ros.org/wiki/eros
Embedded Control Libraries: http://snorriheim.dnsdojo.com/redmine/wiki/ecl
_______________________________________________
Eros-users mailing list

https://code.ros.org/mailman/listinfo/eros-users