Age | Commit message (Collapse) | Author | Files | Lines |
|
Add dissection of OMA-ILP
svn path=/trunk/; revision=52721
|
|
-Wshorten-64-to-32 to CXXFLAGS. Also, add AM_CLEAN_FLAGS to AM_CXXFLAGS, not AM_CPPFLAGS.
svn path=/trunk/; revision=52676
|
|
svn path=/trunk/; revision=52674
|
|
to CFLAGS and/or CXXFLAGS as needed.
svn path=/trunk/; revision=52654
|
|
compiler flags checks.
svn path=/trunk/; revision=52649
|
|
svn path=/trunk/; revision=52647
|
|
of warnings described at
http://petereisentraut.blogspot.com/2011/05/ccache-and-clang.html
svn path=/trunk/; revision=52646
|
|
svn path=/trunk/; revision=52548
|
|
for strtoll() (if we ever did check for it).
svn path=/trunk/; revision=52519
|
|
Remove unused NEED_G_ASCII_STRTOULL_H
svn path=/trunk/; revision=52385
|
|
svn path=/trunk/; revision=52321
|
|
Contents/Frameworks since that's what macdeployqt expects. Have
osx-dmg.sh look at the correct executable.
svn path=/trunk/; revision=52295
|
|
svn path=/trunk/; revision=52293
|
|
installers.
svn path=/trunk/; revision=52292
|
|
svn path=/trunk/; revision=51923
|
|
on PPC.
svn path=/trunk/; revision=51921
|
|
quoting characters; use test instead.
svn path=/trunk/; revision=51503
|
|
installing command-line developer tools with no SDKs but with a standard
UN*Xy /usr/include or of installing Full Frontal Xcode, if the user
didn't specify building against an SDK, check to see whether we *have*
any SDKs and, if not, don't set the deployment target.
svn path=/trunk/; revision=51501
|
|
configure Wireshark, so we don't, for example, do "make distcheck" with
no options, and thus default to GTK+ 3, on a system without GTK+ 3 where
Wireshark was configured with --with-gtk2. (This also means that if
we're configuring only with Qt, or with GTK+ *and* Qt, "make distcheck"
will check with those.)
svn path=/trunk/; revision=51456
|
|
the kernel" thing, and add the NetBSD and DragonFly BSD /proc links (if
they don't mount /proc, that doesn't work, but it doesn't get in the
way).
On Solaris, check for getexecname, just in case somebody tries to build
on an old Solaris that doesn't support it (that could well end up being
the least of their problems, but at least they won't ask us to diagnose
that one).
svn path=/trunk/; revision=51343
|
|
That way, if somebody specifies --with-gtk[23] and that version of GTK+
isn't found, we fail with an indication that the version of GTK+ they
asked for isn't there, and if no GUI toolkit was specified, and they
didn't explicitly say "don't build Wireshark", we look for GTK+ 3 and,
if it's not found, let the user know explicitly.
svn path=/trunk/; revision=51323
|
|
it succeeds, so there's no point in checking whether it succeeds in a
sample program.
svn path=/trunk/; revision=51322
|
|
try it without -ldl (in case the OS doesn't have it - not a good idea,
as it complicates the build process for cross-platform tools that might
require it on other platforms, but "not a good idea" never stopped UN*X
vendors in the past) and, if that fails, try it with -ldl.
svn path=/trunk/; revision=51309
|
|
New dissector for Air/Ground Datalink ICAO doc 9705 Ed2: ULCS, CM, CPDLC.
Add the files to the distribution.
svn path=/trunk/; revision=51212
|
|
svn path=/trunk/; revision=51161
|
|
r51128. Print a warning if we're building with Python < 2.5.
svn path=/trunk/; revision=51158
|
|
and Python 3.
svn path=/trunk/; revision=51077
|
|
svn path=/trunk/; revision=51075
|
|
svn path=/trunk/; revision=51074
|
|
deployment target; if --disable-osx-deploy-target was specified, set it
to the OS version on which we're building - minor/dot-dot version and
all - as there's no guarantee that it'll work on *any* version earlier
than that.
svn path=/trunk/; revision=51060
|
|
anything other than OS X, fail; whatever it is you're trying to do won't
work (unless and until there exists a platform that fully supports
cross-development for OS X, *including* building against SDKs and
building with -mmacosx-version-min).
If you use neither on OS X, default to the OS major version on which
you're building. If you use --disable-osx-deploy-target, don't build
against an SDK and don't use -mmacosx-version-min.
svn path=/trunk/; revision=51057
|
|
packages, providing macros that we use in our configure script in case
somebody building from SVN doesn't happen to have the package installed
and thus doesn't happen to have those macros defined.
In the case of Qt, there *isn't* such a .m4 file, so we had to create
the macro. Move it to acinclude.m4, and rename it to
AC_WIRESHARK_QT_CHECK to indicate that it's our own check.
svn path=/trunk/; revision=50881
|
|
svn path=/trunk/; revision=50879
|
|
--disable-wireshark was not specified, build with GTK+ 3.
If any of --with-gtk2 or --with-qt are specified, and --with-gtk3 wasn't
specified, *don't* look for GTK+ 3 and don't build with it.
If *both* --with-gtk2 and --with-gtk3, fail.
svn path=/trunk/; revision=50872
|
|
autotool, cmake and nmake.
No idea what it takes to change the visual project stuff
svn path=/trunk/; revision=50863
|
|
for both autotools and cmake builds
(in order to use getopt_long(), we have to check if we
can include getopt.h)
svn path=/trunk/; revision=50680
|
|
since now the defaults work as they should.
svn path=/trunk/; revision=50644
|
|
@executable_path/../lib as well as /usr/local/lib, so we can use @rpath
in the install names in the executables and libraries in the application
bundle.
Have the osx-app.sh script tweak all references to libraries from
/usr/local/lib in all executables, libraries, and plugins in the app
bundle to use @rpath. (The "all" is important; it fixes the GTK+ crash
mentioned in the comment in osx-app.sh. The notion of doing all of them
came from the osx-app.sh script in a newer version of Inkscape.)
This renders the setting of DYLD_LIBRARY_PATH in the wrapper scripts in
the bundle unnecessary; remove it. (Ideally, we should try to get rid
of the wrapper scripts entirely, but that might have to wait for us to
switch to using Qt.)
svn path=/trunk/; revision=50560
|
|
the flags for the C++ compiler.
If we're building for 10.5, force a 32-bit build.
svn path=/trunk/; revision=50459
|
|
svn path=/trunk/; revision=50440
|
|
tests using the compiler are done using the flags that
we'll be using when building.
Add a -mmacosx-version-min flag to CFLAGS/CPPFLAGS/LDFLAGS so that the
compiler tests use them. This may, or may not, obviate the need to set
MACOSX_DEPLOYMENT_TARGET in OSX_DEPLOY_TARGET.
svn path=/trunk/; revision=50426
|
|
when building for OS X; that causes the MACOSX_DEPLOYMENT_TARGET
environment variable to be set when building (so that, for example, we
don't use linker features available on the version on which we're
building but not on the minimum OS version for which we're building),
and causes the SDK for that version to be used (so that, for example, we
don't link with libraries with later version numbers than the ones
provided with the OS version for which we're building).
svn path=/trunk/; revision=50410
|
|
AC_WIRESHARK_COMPILER_FLAGS_CHECK, because it doesn't just affect CFLAGS
and it doesn't just affect the flags for GCC.
svn path=/trunk/; revision=50222
|
|
that it doesn't fail due to the C++ compiler not supporting -W options
that the C compiler does.
(We should fix that, too, by having separate checks for whether the C
and C++ compilers support particular options.)
svn path=/trunk/; revision=50215
|
|
rather than #include <iostream.h>.
Also reference cout as std::cout in the test program.
svn path=/trunk/; revision=50206
|
|
macro, and mustn't include that itself.
svn path=/trunk/; revision=50205
|
|
C++ compiler (it might not be one on, for example, OS X, due to "cc"
being a C compiler, "CC" referring to "cc" due to the case-insensitivity
of the default OS X file system, and "CC" being one of the names checked
for in AC_PROG_CXX), so if we really need a C++ compiler, test it with a
program that a C compiler won't compile.
svn path=/trunk/; revision=50204
|
|
on a Mac, right? So of *COURSE* you want to use our shiny new frameworks
rather than those ugly old open-source multi-platform libraries, right?"
warnings.
svn path=/trunk/; revision=50200
|
|
bugs it points out that probably mean the code won't work on machines
that require alignment (e.g., SPARC machines), but we'll turn it on once
we fix them. (clang is fussier than GCC about this.)
svn path=/trunk/; revision=50187
|
|
an error, or not issue warnings, by default if you give them an unknown
-f flag. Instead, test that flag with all compilers, and use -Werror to
force it to error out.
As with C/C++ flags, so with C++-only flags.
svn path=/trunk/; revision=50178
|