far2l
far2l copied to clipboard
elfmz
scp and crossload to the same host
When both panels use the same SCP connection to same SCP host, why do we need to download and upload files when doing copy and move? Can't we just do "cp" and "mv" on a server side?
1 Still only limited functionality possible - no visible progress etc 2 Too narrow usecase 3 Also you may just run far2l remotely there and you'll get this and more
Spent two evenings investigating how to build far2l for openwrt/ddwrt. They even have no glibc there, musl or uClibc is used instead. Also mips architecture. Cross compilation with also cross compiling half of deps with another c lib... Not an easy task.
About progress — may it be an option disabled by default?
Building far2l for such minimalistic env is separate issue. Theoretically it must be buildable, may be with some missing plugins, like colorer (due to xerces dependency), anx wx of course is under big question, but other parts should work.
tried to crosscompile under buildroot for arm and eventually faced with issue that farlng (iternal tool) needs to be built for host arch.. may be rewrite it in perl to simplify cross-compilation? Otherwise need to do it in two phases - one host compilation another - cross compilation partially using results of host build..
As for target architecture, the router I can test build on is big endian mips with uClibc: system type : Atheros AR9132 rev 2 (0xb9) cpu model : MIPS 24Kc V7.4
Do I understand right that for build process only "generator" mode is required?
yes, i already bit started implementing such lightweight (hardread) perl generator so dont bother.. for now)
router is big endian? it can make some troubles :)
Just googled "AR9132" a bit. Could not find data sheet. Found this: https://github.com/Deoptim/atheros/blob/master/JTAG/AR9132.cfg:
target create $TARGETNAME mips_m4k -endian big -chain-position $TARGETNAME
The same is written here: https://www.virtualhere.com/comment/1276#comment-1276 One more proof: https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=636565&sid=0e6b3141d3d64abafe63754f6ba3d3bc#636565
As embedded systems are often single user, we can introduce embedded build mode without sudo releated stuff to save build time and storage space.
tried to crosscompile under buildroot
Isn't buildroot a tool for generating firmware images, not individual software packages?
yes, but IMHO its cross compilation as target is not same as host
I just don't really understand how to make build, for example, for a openwrt/ddwrt router. Okay, I can tell cmake to use a different compilation toolchain with a different target platform, but where do I get the necessary header files for different libraries, and how do I tell cmake to use them, not the system ones?
need to google steps for it.. isnt it this: https://openwrt.org/docs/guide-developer/toolchain/crosscompile ?
need to google steps for it.. isnt it this: https://openwrt.org/docs/guide-developer/toolchain/crosscompile ?
Unfortunately, this is nothing there about where to get headers for dependency libs and how to pass them to cmake. Some search gives me two cmake examples, an application and a library it depending on: Libubox Ubox
But it still does not explain, how ubox build recipe knows where to get libubox header files. Ubox CMakeLists.txt has INCLUDE_DIRECTORIES(/opt/local/include). But I still do not understand a way how library header files for target platform should appear at this path.
From link above:
If compilation aborts due to missing header files or shared objects, you might need to override CFLAGS and LDFLAGS to point to the staging_dir/target-architecture_uClibc-libcver/usr/include and …/usr/lib directories
So first you have to compile full buildroot image for your device - it will build also toolchain, libc and then compiler and necessary headers will be useable
So first you have to compile full buildroot image for your device - it will build also toolchain, libc and then compiler and necessary headers will be useable
Yes, got it. But this is about system libs. And that about headers for libs that far2l depends on like libxerces? However, such dependencies seem to apply only to plugins. In theory, far2l itself should build without them, right?
Yes, buildroot appeared to have xerces and many others (but no wx and no uchardet), dependencies are decribed in buildroot package files that i've just added (however they little bit drafts for now, need some refinement) - need just to add them to buildroot/packages directory, then reference added package from some category in packages/Config.in then run make menuconfig and enable there far2l - then make - and it will create full image with far2l and libs inside
At least thats how i was able add far2l into image i build for my Olinuxino Lime2 that i use as kind of smart home brains :)
You mean I should build dependencies in buildroot also? But many of them, like libssh, are already availble as openwrt packages, seems better to use them to save router space.
Building them needed to get properly configured headers and libs, no need to copy them on target if they're already there
Got it, thanks! And libs abi stays the same within changes of minor versions, am i right?
There is still two use cases for "crossload via cp/mv" feature:
- router has too little flash memory to install far2l
- router has ssh, but do not support installing any additional software