Long build times for loam_mapping/loam_feature_extract about fast_lio HOT 12 CLOSED

Thanks for your interest. But I didn't meet this problem. Would you please tell me the actual cpu type?

from fast_lio.

I use a Nvidia Jetson AGX Xavier which has an ARM-based processor.

Are you cross-compiling the code or are you directly compiling the code on the target machine (i.e. the dji manifold computer)?

from fast_lio.

from fast_lio.

from fast_lio.

I use a Nvidia Jetson AGX Xavier which has an ARM-based processor.

Are you cross-compiling the code or are you directly compiling the code on the target machine (i.e. the dji manifold computer)?

We are currently working on the implementation on the ARM based platform. The long building time truely exists, several minutes (around 3 minutes) should be taken in my tests.

from fast_lio.

你的编译成功了吗？我的manifold2-c已经第二次出现扩展板损坏，原因可能是电路设计的问题，维修了两次。所以，我也在考虑是否更换成你的这个mini计算机，希望能得到你的帮助！ 谢谢🙏！
…
------------------ Original ------------------ From: mbcel @.> Date: Wed,May 5,2021 3:35 AM To: hku-mars/FAST_LIO @.> Cc: Subscribed @.***> Subject: Re: [hku-mars/FAST_LIO] Long build times for loam_mapping/loam_feature_extract (#14) I use a Nvidia Jetson AGX Xavier which has an ARM-based processor. Are you cross-compiling the code or are you directly compiling the code on the target machine (i.e. the dji manifold computer)? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

You may consider trying intel NUC, its hardware is more stable than manifold 2c and sells cheaper. Only problem is the weight may be a little bigger than manifold 2c.

from fast_lio.

Hm okay. What puzzels me is that this long build time occures on every code change in the laserMapping.cpp file. It seems like the linking process here takes over a minute and needs to be done on ANY change.

Do you experience the same on your ARM platform or do you have such long build times only for the first initial build?

If yes, how do you cope with this? Are you cross-compiling on a different machine or something like that? To wait more than a minute after each code change makes it impossible for me to code properly.

from fast_lio.

from fast_lio.

from fast_lio.

what about raspbery pi 4 arm arhitecture?

from fast_lio.

from fast_lio.

what about raspbery pi 4 arm arhitecture?

fast-lio can work on raspberry but remember to close rviz since rviz will consume too much computing resources.

from fast_lio.