On Wed, May 01, 2013 at 02:37:56PM -0400, Jasper St. Pierre wrote: > config.h is generated by automake. Actually, config.h is generated by running ./configure. > You will need to use autoconf / automake No, you will not need them for normal compilation from tarballs. The GNU build system is constructed precisely with that goal that such special tools are only needed on the developer's system, *not* on the target system where you compile the programs or libraries. > On Mon, Apr 29, 2013 at 11:41 PM, Phyllis <yihsun817@xxxxxxxxx> wrote: > And because compile environmet setting, I should build it without using > Makefile.in and Makefile.am. What exactly prevents you from running configure? You don't have anything like a POSIX shell there and can't have anything like that there? > So I put all *.c and *.h of Pango source code into a folder and compile > them with gcc. This approach might go smoothly for hello-world. But the build process of most packages is much more complex. If you want to replicate it you must study very carefully what the original Makefiles do. > Where is this config.h? which one I should include? config.h is generated by configure from config.h.in and contains all kinds of information gathered about the system. You have to fill the information manually. It is likely you will need handle similarly a number of other files. Yeti _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gtk-list
