DSL Tips and Tricks :: easier way to compile stuff for DSL

Quote

However, I don't see the point in putting any focus at all on Debian packages when building a compiling system

What I should have said is that where a particular application/library does not exist in DSL, I used a binary closest in version number to the woody application/library in order to have something from the same era and thus likely to work with DSL/compile applications that will work with DSL

One thing I'd forgotten to mention is a real-life example of what results from assuming that files extracted from Debian packages are good enough to pass as compatible with DSL.

The ImageMagick myDSL extension has a consistent minor flaw in the gui that will present the user with a warning message if the file selector is cancelled. This happens every time i do this in a vanilla DSL. However, the bug does not show when the application is first compiled, while gcc1-with-libs is still installed. In other words, gcc1-with-libs creates applications that are not entirely compatible with vanilla DSL.

Quote

I used a binary closest in version number to the woody application/library in order to have something from the same era and thus likely to work with DSL/compile applications that will work with DSL

You're probably right in assuming that it will be likely to work. Most of my comments were related to using binaries from Debian as requirements for building a DSL application from source. Unless the library is the *exact* version found in vanilla DSL, I'd say it's not entirely suitable for this task. Maybe I misunderstood what you were talking about (but that's the topic).

Unfortunately, as time passes the older debian binaries become outdated and are left behind. The only way to continue experiencing new features and fixes in these apps is either to keep DSL current (or nearly current) with Debian package management or to compile the newer versions of applications from source, specifically targeted to DSL. I'd opt for the latter, since it would be much easier on DSL development and provide more fexibility to application builders.

Quote

version number to the woody application/library in order to have something from the same era

Often that isn't necessary because newer minor versions of libraries are not supposed to break binaries that depend on earlier minor versions. Then you can compile newer versions of dependent libraries than on dsl and then compile some prog that needs these against their headers and overwrite the old libraries (or keep them seperate in a uci or a different location).

Re: throwing away Debian and compiling from scratch - that's what I was getting at when I was suggesting the T2 build system to Robert.

I also think compiling a new base from scratch would be best. But doing it DSL would throw away all the Debian compatibility still left. I wouldn't mind, as I never used that, and prefer compiling from source.

Robert has too mentioned Debian compatibility isn't important to him..

hello guys,
could someone please explan to a not-very-knowledgeble-person how to "compile from source" in DSL?
just wanted to install flphoto, downloaded their source code - i don't know the next step

i have dsl in debian hard drive installation, 60 mb ram, 5 gb hard disk, compaq old laptop.
cheers

Next Page...
original here.