On 13/03/2014 00:45, Wido wrote: > I know this is kind of off-topic (Raster, you can rant as I know you like > to :D ), but how can I install in another architecture? I mean, compile in > one pc (with the poor's man tar) and make it work in another kind of > computer (like a rPi or tablet, for example).
That's called cross-compiling and one reply on a list isn;t going to give you an answer worth anything. In theory, it's rather simple and it all comes down to you telling the compiler "yes, yes, yes, I know your default setting is to build for the native environment on *this* host, but what I want you to do is use *those* headers over there (the arm ones), build arm code, and put the output files in *that* special place (so they don't clobber my existing native stuff)". Then you press the red Go button and go make coffee. That's the theory. In practice, it involves a whole world of pain if you have not already set up a proper cross-build environment. Jeff can tell you all about it, I believe he has done this very thing (built an arm distro plus E packages) for Bodhi. Feel free to Google "cross-compiling" to find out exactly what's involved. > > I know that kind of thing is a mess with video drivers and stuff, I'm more > curious about the process itself. > > > 2014-03-11 5:13 GMT-03:00 Carsten Haitzler <[email protected]>: > >> On Tue, 11 Mar 2014 09:03:21 +0100 Pierre Couderc <[email protected]> >> said: >> >>> Well, db pakages are fantastic for the users... if there is a maintainer >> >> for users who use debian systems (use the distro you package for) - yes! >> :) for >> others - useless. :) if it is just for personal use, they are overkill if >> you >> know you'll ensure dependencies are there and keep your systems >> homogeneous (ie >> same distro with same deps/version). that's what i do - my syste,s mostyl >> run >> the same distro and i keep them up to date to the same "newness" give or >> take a >> few weeks of updates at most. >> >>> who does the dirty work, and moreover who does it along the time. >>> "Normal" user does not know an does not have to know "make install" but >>> may use synaptic, or maybe apt-get... >> >> yes. but writing all the deb packaging files and their required content is >> a >> fair bit of hunting down info and messing with lots of files. vs poor mans >> tarball, it's much more work. just saying. if you re happy to do the work - >> then do it! :) >> >>> Le 11/03/2014 01:25, Carsten Haitzler (The Rasterman) a écrit : >>>> in effect deb pkgs (rpm and others) do the above work for you.. and >>>> then some (handle dependencies, conflicts etc.). i personally have >>>> done the above "poor mans package" often enough as it frankly is far >>>> less work (barrier of entry) than making a proper pkg (be it rpm, deb >>>> or arch pkg), but of the packaging systems out there, debian is by far >>>> the most painful in terms of initial footwork to get a package up. rpm >>>> is next (easier - a single simple generic spec file will do a good >>>> job) and probably arch is next), wityh poor-mans packages (tarballs) >>>> being the easiest. :) -- Alan McKinnon [email protected] ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
