Ignore:
Timestamp:
Nov 20, 2003, 5:54:04 PM (17 years ago)
Author:
Sam Hocevar
Message:
  • debian/control: + Changed section to libs/libdevel instead of games/games. + Changed package name to libcaca-dev.
  • debian/rules: + Use debian/compat instead of DH_COMPAT. + Install README, BUGS and TODO into /usr/share/doc.
  • caca-config.in: + First version of the config script.
  • configure.ac src/Makefile.am: + Build a static PIC library as well.
  • README TODO: + Various updates.
Location:
libcaca/trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • libcaca/trunk

    • Property svn:ignore
      •  

        old new  
        1212*-stamp
        1313INSTALL
         14caca-config
  • libcaca/trunk/README

    r189 r202  
    1313     ./configure --enable-conio --host=i386-pc-msdosdjgpp
    1414
     15
     16Using libcaca
     17
     18   o  Compiling a libcaca program is fairly simple:
     19
     20      gcc -c foobar.c -o foobar.o `caca-config --cflags`
     21      gcc foobar.o -o foobar `caca-config --libs`
     22
     23   o  If you are writing a shared object that uses libcaca, either a
     24      dynamically loadable plug-in or a shared library, you should use
     25      the `--plugin-libs' flag for libcaca:
     26
     27      gcc -fPIC -c libfoo.c -o libfoo.o `caca-config --cflags`
     28      gcc -shared libfoo.o -o libfoo.so `caca-config --plugin-libs`
     29
     30
     31Binary packages
     32
     33   o  As the API is not stable yet, everyone should statically link libcaca
     34      with their programs or libraries. DO NOT DISTRIBUTE SHARED VERSIONS
     35      OF LIBCACA.
     36
Note: See TracChangeset for help on using the changeset viewer.