Hi
Thanks for the script. Was what I was looking for. But, the thing is
messed up. Fixated on static versions and download urls, for one
thing. If something goes wrong during download, the whole process is
started again. And doing the whole thing without macport is strictly
speaking a painful process.
It works with autotools, but doesn't with cmake. But is this not the
whole point for cmake in the first place?
Some of the things I noticed so far:
* Disabling werror is a necessity, but not specific to Mac
* -fexcess-precision=fast needs to be disabled for llvm-clang with
XCode 4.3 in CMakeLists.txt
* Wireshark segfaults in glib if run with macports version still
installed on the system
I'll send a patch regarding cmake support, as well as an updated
version of that script, when I get around it.
regards,
Roland
On Sat, Mar 23, 2013 at 7:54 PM, Guy Harris <guy@xxxxxxxxxxxx> wrote:
>
> On Mar 23, 2013, at 7:51 AM, Roland Knall <rknall@xxxxxxxxx> wrote:
>
>> Can someone point me in the right direction on how to build wireshark
>> successfully using Mountain Lion? So far I am failing spectacularly.
>> Using MacPorts for the necessary libraries and dev-dependencies, and
>> deactivating everything I can not compile (Airpcap amongst those)
>
> Using Xcode's command-line tools, autoconf/automake/libtool downloaded in source code form from the GNU project's server and installed (because Mountain Lion doesn't supply them), and the top-level macosx-setup.sh script to set up the necessary libraries and developer, I can compile.
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe