I did it in different installers, though unfortunately, how can I actually do it or can not remember who From the program this feature is why I can learn from them.
I essentially am compiled a shared library (not yet with Otokonf / Libutol, just compile all files in a standard Mesefail) and Mesefail format what is provided to compile this wildcard Does it? I know that you are automatically asking for a mechanism to create a The source files in the directory, but I dislike that approach; At some point in the future, a person will have to test or disable two, and you are making a bit weird, such as renaming a file, it will not be automatically compiled. I really like every program that you intend to create in Here AppArmor looks like regression test suite is a snippet that something like this (I have hope I copy all related bits, it has been a few years .) This is not that easy, just leaving a new file in the directory; You need to add it to test simply examples file that is attached to the library (ie
../ bin / libfoo.so.1.0.1 )
Makefile , but it does not need to be awesome. With some you can easily create all your
.c files in the
.o files or in the executable directly.
SRC = access.c \ changeprofile.c \ changehat.c \ changehat_fork.c \ changehat_misc.c \ .... unlink.c \ xattrs.c ... #only x86 derived ioperm / iopl test architecture ifneq, (if $ $ $ (shell uname -i), i386 i486 I586 i686 x 86 x86_64)) SRC + = syscall_ioperm.c syscall_iopl.c endif ... LIBIMMUNIX: = $ (shell if [-f /usr/lib/libapparmor.so -o -f /usr/lib64/libapparmor.so]; then \ echo -lapparmor; \ elif [-f /lib/libimmunix.so.1 -o -f / lib64 /libimmunix.so]; then \ echo -limmunix; \ fi) CFLAGS + = $ (CHANGEHAT_FLAGS) -l-Wastrik -prototypes LDLIBS + = $ (LIBIMMUNIX) EXEC = $ (SRC:%. C =%) ... All: $ (EXEC) changehat.h
makefile but you only need to add a name to a line, and this is for good if you want to disable it, then comment on the offensive line Approximately is as easy and fairly over control on your build process.
Comments
Post a Comment