> In other words, there will be new .c files that should be compiled
> only
> for the windows version and some .c files exclusive to the linux version.
> Suppose also I want to specify this at configure-time (e.g.
> "./configure" builds linux, "./configure --enable-win32" builds windows).
>
Hello,
I am a bit lost here. We recently started a project using GNU Build
System in order to make our package installable everywhere without mysteries
of package-specific builds.
Now I am facing a problem I will try to explain with an easier to
understand example.
Suppose I am making
Dave Hart wrote on 2011/12/05 19:17:26:
> On Mon, Dec 5, 2011 at 17:33, Joakim Tjernlund
> wrote:
> > One thing that would go a long way is if one could do something like this:
> > make install eq_ss
> > and have make just install what is in the eq_ss directory
>
> As long as subdirectories of e
On Mon, Dec 5, 2011 at 17:33, Joakim Tjernlund
wrote:
> One thing that would go a long way is if one could do something like this:
> make install eq_ss
> and have make just install what is in the eq_ss directory
As long as subdirectories of eq_ss are intended to be installed as well:
cd eq_ss
m
"Ralf Wildenhues" wrote on 2011/12/05 17:27:35:
>
> Hello Joakim,
>
> * Joakim Tjernlund wrote on Wed, Nov 30, 2011 at 08:11:31AM PST:
> > Question: "make install" always install all targets, even if some of then
> > haven't been rebuilt
> > since last install. Is it possible to have some depende
Hello Joakim,
* Joakim Tjernlund wrote on Wed, Nov 30, 2011 at 08:11:31AM PST:
> Question: "make install" always install all targets, even if some of then
> haven't been rebuilt
> since last install. Is it possible to have some dependency sensitive install
> so only rebuilt
> targets are reinsta
