libc 4, a.out - DAIICT Intranet

More documents

Recommendations

Info

# Write your program, keeping portability in mind. Create "Makefile.in". # Run "autoscan". # Rename "configure.scan" to "configure.ac" # Run "autoheader". # Run "autoconf". # "./configure". # Check "config.h". If necessary, modify source and repeat from step #2. # And lastly, compile!
What is Automake? Automake is a program that will automatically generate the "Makefile" for you. Although we already have a working "Makefile", it's not quite portable. For example, should the Makefile use "cc" or "gcc"? Or should the name of the executable be "myprog" or "myprog.exe"? Portability doesn't only affect our sourcecode, but our Makefile as well.
Page 1 and 2: Linux Library Handling The possible
Page 3 and 4: How to compile programs with Autoto
Page 5 and 6: Autotools is a collection of three
Page 7 and 8: Listing of "Makefile" # Makefile: A
Page 9 and 10: Let's add Autoconf First, we create
Page 11 and 12: $ mv Makefile Makefile.in $ ls Make
Page 13 and 14: Let's review what we've done so far
Page 15 and 16: ●But we don't have "config.h" yet
Page 17 and 18: Notice how "autoheader" generates "
Page 19 and 20: ●config.h : There are some consta
Page 21 and 22: $ autoscan Use of uninitialized val
Page 23 and 24: Notice a few things here: ● After
Page 25 and 26: * Define to 1 if you have the head
Page 27 and 28: Using this header file, we can chec
Page 29: A separate function to handle the t
Page 33 and 34: Here's the "Makefile.am" we'll be u
Page 35 and 36: Dealing with errors Now, let's run
Page 37 and 38: As for the errors about PACKAGE and
Page 39 and 40: So, here is how we can use Automake

libc 4, a.out - DAIICT Intranet

Create successful ePaper yourself

Delete template?

Save as template?