In the past, i found it best to make myprojectexe use myprojectlib in place, without an installiert step inbetween. Am 09.12.2012 22:28 schrieb "Germán Diago Gómez" <germandi...@gmail.com>:
> Hello all, > > I don't know if this is the correct mailing list to ask because it's a > question that affects both autoconf (for configuration) and automake > (the order in which targets are run). I find the same problem of having > a library to support one project and the executable for that project > with a (simplified) typical structure: > > mywholeproject/ > libmyproject/ > myprojectexe/ > > The problem I usually find is that myproject exe depends on > libmyproject, but when myprojectexe is going to be compiled, > libmyproject pkgconfig file is not installed yet. What is the correct > approach to solve this dependency? I wonder if make install would behave > better if instead of doing: > > 1.- Build subproject libmyproject > 2.- Build subproject myprojectexe. > 3.- Install subproject libmyproject. > 4.- Install subproject myprojectexe. > > it executed the sequence were 1, 3, 2, 4? This way pkgconfig could find > the .pc file without any problem since it would be already installed. > Am I missing anything here? > > Regards > > >