I was able to get it to work by using autotools from MacPorts, e.g.: PATH=/opt/local/bin:$PATH autoreconf -fiv
This version has pkg-config and the correct macros. I disagree, in general, with the philosophy that users should develop against the tarball rather than SVN. However, I really don't have time to argue any more about this. I am checking in a patch to disable GNU TLS by default, since we all seem to agree on that much at least. On 4/29/10 2:54 AM, Pierre Ossman wrote: > On Thu, 29 Apr 2010 02:33:24 -0500 > DRC <dcomman...@users.sourceforge.net> wrote: > >> OK, well, if PKG_CHECK_MODULES is going to be used, then I strongly >> believe that we should: >> >> (a) not enable GNU TLS support by default. Otherwise, whenever someone >> tries to build on Windows or Mac or any other platform that doesn't have >> GNU TLS, the build will fail. > > Agreed. This is wrong. > >> >> (b) include the PKG_CHECK_MODULES macro for systems that don't have it. >> >> I don't know why you say "there must be a third-party addon of >> pkg-config for Xcode". That's not the way Apple works. The only reason >> why the system has pkg-config at all is because the Mono framework >> includes it, and I doubt that this is even installed by default. It >> certainly isn't part of the regular Xcode install. > > A quick google reveals that there are more things than Mono that want > pkg-config. So this is hardly an obscure problem for Mac people. > >> >> I am a strong believer that an open source project should try its best >> to be buildable using the default toolchain on a given platform. > > I don't agree. Trying to cater to every build environment with a > single build system is neigh impossible, and few projects have the > manpower to keep multiple systems in place. pkg-config can be considered > a standard part of the autotools repertoire so if Xcode lacks that then > I'd say that an autotools build system is wrong for that environment. > > So I'd say that the options are: > > - Require that the platform is adapted to follow our needs (which is > what we have done with Windows since we moved to mingw) > > - Have multiple build systems, one for each build environment we > intend to support. > > I only see the first option as realistic. > >> There is no reason why a Mac user would need (or want) to build >> Xvnc. I'm just trying to make it as easy as possible to build >> vncviewer. It seems ridiculous that someone should have to download, >> build, install, and configure pkg-config just so it can tell them that >> they don't have GNU TLS. > > Users don't have to. As Alan pointed out, pkg-config macros are only > needed when working with svn. Users should be building from the tar > balls. > > And installing pkg-config is not that difficult. It's also not > unthinkable that this project will grow more dependencies that aren't > included on a standard Mac OS install. If you want to build something > yourself then you really need to be prepared that there are > dependencies you need to sort out first. > > Rgds ------------------------------------------------------------------------------ _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
