I have tried for several days to build an OSX app that can run on other systems. I can run both cli and app wireshark on my build machine (mountain lion). But when i try to run the app on another mountain lion machine, there are libraries missing, etc. I've added some of those libs manually, but now i seem to have dependencies on two different versions of libiconv. Are the scripts in SVN supposed to work to build a a stand-alone app on mountain lion? Have I missed some flags that should be set? I've used different combinations of macosx-setup, autogen, configure, osx-app, etc. but to no avail. Has anyone successfully built a ML app from the SVN sources? asked 23 Apr '13, 22:33 jmfinn9 edited 25 Apr '13, 09:45 |
2 Answers:
I have solved my problem - it was because I had macports installed on my development machine. Once I removed macports, I was able to easily build the macos app with the supplied make target. Thanks everyone for their input. answered 25 Apr '13, 07:50 jmfinn9 |
After you ran If not, do so. If you just run (This has nothing to do with Mountain Lion, BTW; it's true for all OS X releases.) answered 23 Apr '13, 23:01 Guy Harris ♦♦ |
Thanks for the quick reply. I have tried building the package, but packagemaker (which is now deprecated by Apple) throws an exception and crashes. I'll revisit that, though. Has anyone run packagemaker in ML? Is it just crashing on my system?
I manually built the package with the package manager, but still had the same error. After further investigation - it seems that some parts of wireshark require version 7.0.0 of libiconv and some parts require version 8.0.0 of libiconv. I have not been able to get around this yet.
Has anyone successfully built the stand-alone osx app from either the current svn or the latest source tarball?
@jmfinn9 Your "answer" has been converted to a comment as that's how this site works. Please read the FAQ for more information.
I've run packagemaker on my 10.8.2 system with Xcode 4.6, build version 4H127, so it definitely works on 10.8.2 with that build of Xcode 4.6, at least. Apple may have broken something in a later Xcode release or in 10.8.3; if so, you might have to find a later version of Auxiliary Tools for Xcode - go to Downloads for Apple Developers (you'll need an ADC account for that), and search for "Auxiliary Tools for Xcode" and see whether a later version helps.
Thanks graham for fixing my mistake.