[haiku-development] Re: An idea about compiling applications
- From: James Leone <linuxcpa@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 21 Jul 2014 11:27:17 -0700
Some more elaboration...
If this configuration file were community maintained and available to
download and could be updated, it could do a lot to "instapatch"
configuration files.
It could have:
1. If/then capabilities so identical original functions can have more than
1 resolution if necessary, or as function differences evolve
2. A way to insert patches in the appropriate relative location within the
configure file
3. A way to auto create patches and recipes and auto upload to a holding
place at Haikuports.org for review/approval
James Leone
On Mon, Jul 21, 2014 at 11:00 AM, James Leone <linuxcpa@xxxxxxxxx> wrote:
> To start off, I'll say up front that I have near zero programming skills.
> I have compiled applications before, but of course, that's after all of the
> very difficult work had been done for me.
>
> So I don't know if what I am about to attempt to describe is an actual
> impossibility. All I know is that I would like to help somehow.
>
> I wish I was able to contribute by compiling applications. But at my skill
> level, I can't do much more than download some code and typing ./configure
> and make.
>
> So, here is my idea.
>
> Is there a way to eliminate the need for patches by enhancing the way
> configure behaves so that it knows what function calls to substitute in
> when configure runs?
>
> Right now we are maintaining patches over at haikuports.org. I know I am
> far too under-skilled to contribute to that effort in the form of producing
> patches. However, could the process of patch creation be automated somehow?
>
> Based on what I believe (I may not be correct in the slightest) the web
> page I reference below contains a less than complete list of issues that
> will prevent an application from compiling:
>
> http://ports.haiku-files.org/wiki/CommonProblems
>
> My belief is that these patches are applied to a file called configure,
> supplied with the source code for the program.
>
> If a patch to configure is sufficient, configure will be able to create a
> Makefile that will result in a successful compilation.
>
> For example, I copied this patch snippet from the above referenced web
> site:
>
> -AC_CHECK_LIB(socket, socket)
> +AC_SEARCH_LIBS(socket, socket network)
> AC_CHECK_LIB(resolv, inet_aton)
> AC_CHECK_LIB(rt, clock_gettime)
> AC_CHECK_LIB(nsl, inet_ntoa)
>
>
> It appears from the above that the "AC_CHECK_LIB(socket, socket)" function
> is being removed and It is being replaced by:
> 1.) "AC_SEARCH_LIBS(socket, socket network)"
> 2.) "AC_CHECK_LIB(resolv, inet_aton)"
> 3.) "AC_CHECK_LIB(rt, clock_gettime)" and
> 4.) "AC_CHECK_LIB(nsl, inet_ntoa)"
>
> So here is my idea:
>
> Is it possible to make a configuration file for Configure so that
> configure can automatically substitute these functions?
>
> configure.conf
> # Global Function Aliases
> "AC_CHECK_LIB(socket, socket)" = ["AC_CHECK_LIB(resolv, inet_aton)"
> "AC_CHECK_LIB(rt, clock_gettime)" "AC_CHECK_LIB(nsl, inet_ntoa)"]
>
> Opinions?
>
> James Leone
>
> P.S. I probably couldn't make this thing if I tried.
>
>
Other related posts:
