On Thu, 2011-03-31 at 15:41 +0200, Jonas Maebe wrote: > On 31 Mar 2011, at 14:42, Marco van de Voort wrote:
> At least the package I referred to (univint) tends to change > significantly over time. The Mac OS X 10.6 SDK split a bunch of > headers and removed others compared to previous versions (most C > programmers use umbrella headers, so they don't notice that either). > As Carbon gets phased out, more and more things will probably change. > It's not really feasible to manually go through the current list of > dependencies and to update them where necessary. Otoh, replacing them > with a newly auto-generated list currently risks removing code that > someone else added to manually to fix something. > > > The trouble is that makefile.fpc does not contain all information. > > It is not > > a closed system, and has barely enough info to build, and depends on > > the > > autobuilding capacity of the compiler. Something that can't be used > > for > > packaging and other features. > > That's why I mentioned "or any other structured format". It's not a bad idea to see if we can make a structured (and readable) format to create our fpmake.pp files. I was also thinking about letting fpmake detect from the compiler-output if a dependency is missing, and give a warning if this happens, so it can be added. Joost. _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel