Changeset 582:619e79710ec7 in mediastreamer2


Ignore:
Timestamp:
Aug 17, 2009 12:39:59 PM (4 years ago)
Author:
smorlat <smorlat@…>
Branch:
default
Message:

update compilation script to work with August 09 mingw environment.

git-svn-id: ​svn+ssh://svn.savannah.nongnu.org/linphone/trunk@572 3f6dc0c8-ddfe-455d-9043-3cd528dc4637

Location:
linphone
Files:
1 added
6 edited

Legend:

Unmodified
Added
Removed

  • linphone/INSTALL

    r581 r582  
    33 
    44Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, 
    5 2006 Free Software Foundation, Inc. 
    6  
    7 This file is free documentation; the Free Software Foundation gives 
     52006, 2007, 2008, 2009 Free Software Foundation, Inc. 
     6 
     7   This file is free documentation; the Free Software Foundation gives 
    88unlimited permission to copy, distribute and modify it. 
    99 
    … …  
    1111================== 
    1212 
    13 Briefly, the shell commands `./configure; make; make install' should 
     13   Briefly, the shell commands `./configure; make; make install' should 
    1414configure, build, and install this package.  The following 
    1515more-detailed instructions are generic; see the `README' file for 
    … …  
    6868     with the distribution. 
    6969 
     70  6. Often, you can also type `make uninstall' to remove the installed 
     71     files again. 
     72 
    7073Compilers and Options 
    7174===================== 
    7275 
    73 Some systems require unusual options for compilation or linking that the 
    74 `configure' script does not know about.  Run `./configure --help' for 
    75 details on some of the pertinent environment variables. 
     76   Some systems require unusual options for compilation or linking that 
     77the `configure' script does not know about.  Run `./configure --help' 
     78for details on some of the pertinent environment variables. 
    7679 
    7780   You can give `configure' initial values for configuration parameters 
    … …  
    8689==================================== 
    8790 
    88 You can compile the package for more than one kind of computer at the 
     91   You can compile the package for more than one kind of computer at the 
    8992same time, by placing the object files for each architecture in their 
    9093own directory.  To do this, you can use GNU `make'.  `cd' to the 
    … …  
    98101reconfiguring for another architecture. 
    99102 
     103   On MacOS X 10.5 and later systems, you can create libraries and 
     104executables that work on multiple system types--known as "fat" or 
     105"universal" binaries--by specifying multiple `-arch' options to the 
     106compiler but only a single `-arch' option to the preprocessor.  Like 
     107this: 
     108 
     109     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ 
     110                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ 
     111                 CPP="gcc -E" CXXCPP="g++ -E" 
     112 
     113   This is not guaranteed to produce working output in all cases, you 
     114may have to build one architecture at a time and combine the results 
     115using the `lipo' tool if you have problems. 
     116 
    100117Installation Names 
    101118================== 
    102119 
    103 By default, `make install' installs the package's commands under 
     120   By default, `make install' installs the package's commands under 
    104121`/usr/local/bin', include files under `/usr/local/include', etc.  You 
    105122can specify an installation prefix other than `/usr/local' by giving 
    … …  
    124141================= 
    125142 
    126 Some packages pay attention to `--enable-FEATURE' options to 
     143   Some packages pay attention to `--enable-FEATURE' options to 
    127144`configure', where FEATURE indicates an optional part of the package. 
    128145They may also pay attention to `--with-PACKAGE' options, where PACKAGE 
    … …  
    136153`--x-libraries=DIR' to specify their locations. 
    137154 
     155Particular systems 
     156================== 
     157 
     158   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU 
     159CC is not installed, it is recommended to use the following options in 
     160order to use an ANSI C compiler: 
     161 
     162     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500" 
     163 
     164and if that doesn't work, install pre-built binaries of GCC for HP-UX. 
     165 
     166   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot 
     167parse its `<wchar.h>' header file.  The option `-nodtk' can be used as 
     168a workaround.  If GNU CC is not installed, it is therefore recommended 
     169to try 
     170 
     171     ./configure CC="cc" 
     172 
     173and if that doesn't work, try 
     174 
     175     ./configure CC="cc -nodtk" 
     176 
     177   On Solaris, don't put `/usr/ucb' early in your `PATH'.  This 
     178directory contains several dysfunctional programs; working variants of 
     179these programs are available in `/usr/bin'.  So, if you need `/usr/ucb' 
     180in your `PATH', put it _after_ `/usr/bin'. 
     181 
     182   On Haiku, software installed for all users goes in `/boot/common', 
     183not `/usr/local'.  It is recommended to use the following options: 
     184 
     185     ./configure --prefix=/boot/common 
     186 
    138187Specifying the System Type 
    139188========================== 
    140189 
    141 There may be some features `configure' cannot figure out automatically, 
    142 but needs to determine by the type of machine the package will run on. 
    143 Usually, assuming the package is built to be run on the _same_ 
    144 architectures, `configure' can figure that out, but if it prints a 
    145 message saying it cannot guess the machine type, give it the 
     190   There may be some features `configure' cannot figure out 
     191automatically, but needs to determine by the type of machine the package 
     192will run on.  Usually, assuming the package is built to be run on the 
     193_same_ architectures, `configure' can figure that out, but if it prints 
     194a message saying it cannot guess the machine type, give it the 
    146195`--build=TYPE' option.  TYPE can either be a short name for the system 
    147196type, such as `sun4', or a canonical name which has the form: 
    … …  
    151200where SYSTEM can have one of these forms: 
    152201 
    153      OS KERNEL-OS 
     202     OS 
     203     KERNEL-OS 
    154204 
    155205   See the file `config.sub' for the possible values of each field.  If 
    … …  
    169219================ 
    170220 
    171 If you want to set default values for `configure' scripts to share, you 
    172 can create a site shell script called `config.site' that gives default 
    173 values for variables like `CC', `cache_file', and `prefix'. 
     221   If you want to set default values for `configure' scripts to share, 
     222you can create a site shell script called `config.site' that gives 
     223default values for variables like `CC', `cache_file', and `prefix'. 
    174224`configure' looks for `PREFIX/share/config.site' if it exists, then 
    175225`PREFIX/etc/config.site' if it exists.  Or, you can set the 
    … …  
    180230================== 
    181231 
    182 Variables not defined in a site shell script can be set in the 
     232   Variables not defined in a site shell script can be set in the 
    183233environment passed to `configure'.  However, some packages may run 
    184234configure again during the build, and the customized values of these 
    … …  
    199249====================== 
    200250 
    201 `configure' recognizes the following options to control how it operates. 
     251   `configure' recognizes the following options to control how it 
     252operates. 
    202253 
    203254`--help' 
    204255`-h' 
    205      Print a summary of the options to `configure', and exit. 
     256     Print a summary of all of the options to `configure', and exit. 
     257 
     258`--help=short' 
     259`--help=recursive' 
     260     Print a summary of the options unique to this package's 
     261     `configure', and exit.  The `short' variant lists options used 
     262     only in the top level, while the `recursive' variant lists options 
     263     also present in any nested packages. 
    206264 
    207265`--version' 
    … …  
    230288     `configure' can determine that directory automatically. 
    231289 
     290`--prefix=DIR' 
     291     Use DIR as the installation prefix.  *Note Installation Names:: 
     292     for more details, including other options available for fine-tuning 
     293     the installation locations. 
     294 
     295`--no-create' 
     296`-n' 
     297     Run the configure checks, but stop before creating any output 
     298     files. 
     299 
    232300`configure' also accepts some other, not widely useful, options.  Run 
    233301`configure --help' for more details. 

  • linphone/autogen.sh

    r493 r582  
    1515libtoolize --copy --force 
    1616 
    17 intltoolize -c --force --automake 
     17/usr/bin/intltoolize -c --force --automake 
    1818autoheader 
    1919$ACLOCAL -I m4 

  • linphone/configure.in

    r570 r582  
    5757 
    5858 
    59 if test "$mingw_found" = "yes" ; then 
    60         AC_MSG_NOTICE([Hacking libtool to work with mingw...]) 
    61         sed -e 's/\*\" \$a_deplib \"\*/\*/' < ./libtool > libtool.tmp 
    62         cp -f ./libtool.tmp ./libtool 
    63         rm -f ./libtool.tmp 
    64 fi 
     59dnl if test "$mingw_found" = "yes" ; then 
     60dnl     AC_MSG_NOTICE([Hacking libtool to work with mingw...]) 
     61dnl     sed -e 's/\*\" \$a_deplib \"\*/\*/' < ./libtool > libtool.tmp 
     62dnl     cp -f ./libtool.tmp ./libtool 
     63dnl     rm -f ./libtool.tmp 
     64dnl fi 
    6565 
    6666dnl Add the languages which your application supports here. 

  • linphone/m4/exosip.m4

    r199 r582  
    2020        [], 
    2121        [AC_MSG_ERROR([Could not find eXosip2 library with version >= 3.0.2 !])], 
    22         [-losipparser2 -losip2 -lpthread]) 
     22        [-losipparser2 -losip2 ]) 
    2323AC_CHECK_LIB([eXosip2],[eXosip_get_version], 
    2424        [AC_DEFINE([HAVE_EXOSIP_GET_VERSION],[1],[Defined when eXosip_get_version is available])], 
    2525        [], 
    26         [-losipparser2 -losip2 -lpthread]) 
     26        [-losipparser2 -losip2 ]) 
    2727dnl AC_CHECK_LIB([eXosip2],[eXosip_get_naptr], 
    2828dnl     [AC_DEFINE([HAVE_EXOSIP_NAPTR_SUPPORT],[1],[Defined when eXosip_get_naptr is available])], 
    2929dnl     [], 
    30 dnl     [-losipparser2 -losip2 -lpthread]) 
     30dnl     [-losipparser2 -losip2 ]) 
    3131LIBS=$LIBS_save 
    3232LDFLAGS=$LDFLAGS_save 

  • linphone/m4/osip.m4

    r493 r582  
    4141        LDFLAGS=$OSIP_LIBS 
    4242        LIBS_save=$LIBS 
    43         AC_CHECK_LIB(osip2${osip_legacy_version},osip_init, , AC_MSG_ERROR([Could not find osip2 library !]),[-losipparser2${osip_legacy_version} -lpthread]) 
    44         AC_CHECK_LIB(osipparser2${osip_legacy_version},osip_message_init, , AC_MSG_ERROR([Could not find osipparser2 library !]),[-lpthread]) 
     43        case "$target_os" in 
     44                *mingw*) 
     45                        osip_aux_libs= 
     46                        ;; 
     47                *) 
     48                        osip_aux_libs=-lpthread 
     49                        ;; 
     50        esac 
     51        OSIP_LIBS="$OSIP_LIBS $osip_aux_libs" 
     52        AC_CHECK_LIB(osip2${osip_legacy_version},osip_init, , AC_MSG_ERROR([Could not find osip2 library !]),[-losipparser2${osip_legacy_version} $osip_aux_libs ]) 
     53        AC_CHECK_LIB(osipparser2${osip_legacy_version},osip_message_init, , AC_MSG_ERROR([Could not find osipparser2 library !]),[$osip_aux_libs]) 
    4554        LDFLAGS=$LDFLAGS_save 
    4655        LIBS=$LIBS_save 

  • linphone/mediastreamer2/INSTALL

    r579 r582  
    33 
    44Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, 
    5 2006 Free Software Foundation, Inc. 
    6  
    7 This file is free documentation; the Free Software Foundation gives 
     52006, 2007, 2008, 2009 Free Software Foundation, Inc. 
     6 
     7   This file is free documentation; the Free Software Foundation gives 
    88unlimited permission to copy, distribute and modify it. 
    99 
    … …  
    1111================== 
    1212 
    13 Briefly, the shell commands `./configure; make; make install' should 
     13   Briefly, the shell commands `./configure; make; make install' should 
    1414configure, build, and install this package.  The following 
    1515more-detailed instructions are generic; see the `README' file for 
    … …  
    6868     with the distribution. 
    6969 
     70  6. Often, you can also type `make uninstall' to remove the installed 
     71     files again. 
     72 
    7073Compilers and Options 
    7174===================== 
    7275 
    73 Some systems require unusual options for compilation or linking that the 
    74 `configure' script does not know about.  Run `./configure --help' for 
    75 details on some of the pertinent environment variables. 
     76   Some systems require unusual options for compilation or linking that 
     77the `configure' script does not know about.  Run `./configure --help' 
     78for details on some of the pertinent environment variables. 
    7679 
    7780   You can give `configure' initial values for configuration parameters 
    … …  
    8689==================================== 
    8790 
    88 You can compile the package for more than one kind of computer at the 
     91   You can compile the package for more than one kind of computer at the 
    8992same time, by placing the object files for each architecture in their 
    9093own directory.  To do this, you can use GNU `make'.  `cd' to the 
    … …  
    98101reconfiguring for another architecture. 
    99102 
     103   On MacOS X 10.5 and later systems, you can create libraries and 
     104executables that work on multiple system types--known as "fat" or 
     105"universal" binaries--by specifying multiple `-arch' options to the 
     106compiler but only a single `-arch' option to the preprocessor.  Like 
     107this: 
     108 
     109     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ 
     110                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ 
     111                 CPP="gcc -E" CXXCPP="g++ -E" 
     112 
     113   This is not guaranteed to produce working output in all cases, you 
     114may have to build one architecture at a time and combine the results 
     115using the `lipo' tool if you have problems. 
     116 
    100117Installation Names 
    101118================== 
    102119 
    103 By default, `make install' installs the package's commands under 
     120   By default, `make install' installs the package's commands under 
    104121`/usr/local/bin', include files under `/usr/local/include', etc.  You 
    105122can specify an installation prefix other than `/usr/local' by giving 
    … …  
    124141================= 
    125142 
    126 Some packages pay attention to `--enable-FEATURE' options to 
     143   Some packages pay attention to `--enable-FEATURE' options to 
    127144`configure', where FEATURE indicates an optional part of the package. 
    128145They may also pay attention to `--with-PACKAGE' options, where PACKAGE 
    … …  
    136153`--x-libraries=DIR' to specify their locations. 
    137154 
     155Particular systems 
     156================== 
     157 
     158   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU 
     159CC is not installed, it is recommended to use the following options in 
     160order to use an ANSI C compiler: 
     161 
     162     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500" 
     163 
     164and if that doesn't work, install pre-built binaries of GCC for HP-UX. 
     165 
     166   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot 
     167parse its `<wchar.h>' header file.  The option `-nodtk' can be used as 
     168a workaround.  If GNU CC is not installed, it is therefore recommended 
     169to try 
     170 
     171     ./configure CC="cc" 
     172 
     173and if that doesn't work, try 
     174 
     175     ./configure CC="cc -nodtk" 
     176 
     177   On Solaris, don't put `/usr/ucb' early in your `PATH'.  This 
     178directory contains several dysfunctional programs; working variants of 
     179these programs are available in `/usr/bin'.  So, if you need `/usr/ucb' 
     180in your `PATH', put it _after_ `/usr/bin'. 
     181 
     182   On Haiku, software installed for all users goes in `/boot/common', 
     183not `/usr/local'.  It is recommended to use the following options: 
     184 
     185     ./configure --prefix=/boot/common 
     186 
    138187Specifying the System Type 
    139188========================== 
    140189 
    141 There may be some features `configure' cannot figure out automatically, 
    142 but needs to determine by the type of machine the package will run on. 
    143 Usually, assuming the package is built to be run on the _same_ 
    144 architectures, `configure' can figure that out, but if it prints a 
    145 message saying it cannot guess the machine type, give it the 
     190   There may be some features `configure' cannot figure out 
     191automatically, but needs to determine by the type of machine the package 
     192will run on.  Usually, assuming the package is built to be run on the 
     193_same_ architectures, `configure' can figure that out, but if it prints 
     194a message saying it cannot guess the machine type, give it the 
    146195`--build=TYPE' option.  TYPE can either be a short name for the system 
    147196type, such as `sun4', or a canonical name which has the form: 
    … …  
    151200where SYSTEM can have one of these forms: 
    152201 
    153      OS KERNEL-OS 
     202     OS 
     203     KERNEL-OS 
    154204 
    155205   See the file `config.sub' for the possible values of each field.  If 
    … …  
    169219================ 
    170220 
    171 If you want to set default values for `configure' scripts to share, you 
    172 can create a site shell script called `config.site' that gives default 
    173 values for variables like `CC', `cache_file', and `prefix'. 
     221   If you want to set default values for `configure' scripts to share, 
     222you can create a site shell script called `config.site' that gives 
     223default values for variables like `CC', `cache_file', and `prefix'. 
    174224`configure' looks for `PREFIX/share/config.site' if it exists, then 
    175225`PREFIX/etc/config.site' if it exists.  Or, you can set the 
    … …  
    180230================== 
    181231 
    182 Variables not defined in a site shell script can be set in the 
     232   Variables not defined in a site shell script can be set in the 
    183233environment passed to `configure'.  However, some packages may run 
    184234configure again during the build, and the customized values of these 
    … …  
    199249====================== 
    200250 
    201 `configure' recognizes the following options to control how it operates. 
     251   `configure' recognizes the following options to control how it 
     252operates. 
    202253 
    203254`--help' 
    204255`-h' 
    205      Print a summary of the options to `configure', and exit. 
     256     Print a summary of all of the options to `configure', and exit. 
     257 
     258`--help=short' 
     259`--help=recursive' 
     260     Print a summary of the options unique to this package's 
     261     `configure', and exit.  The `short' variant lists options used 
     262     only in the top level, while the `recursive' variant lists options 
     263     also present in any nested packages. 
    206264 
    207265`--version' 
    … …  
    230288     `configure' can determine that directory automatically. 
    231289 
     290`--prefix=DIR' 
     291     Use DIR as the installation prefix.  *Note Installation Names:: 
     292     for more details, including other options available for fine-tuning 
     293     the installation locations. 
     294 
     295`--no-create' 
     296`-n' 
     297     Run the configure checks, but stop before creating any output 
     298     files. 
     299 
    232300`configure' also accepts some other, not widely useful, options.  Run 
    233301`configure --help' for more details. 
Note: See TracChangeset for help on using the changeset viewer.