[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Comment #11 on issue 270 by osu...@gmail.com: Precompiled protoc binary for OS X https://code.google.com/p/protobuf/issues/detail?id=270 You could also try this: https://github.com/os72/protoc-jar https://github.com/os72/protoc-jar-maven-plugin Either directly via java -jar ..., or extract the packaged OSX protoc from the JAR -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Comment #10 on issue 270 by forrest@gmail.com: Precompiled protoc binary for OS X https://code.google.com/p/protobuf/issues/detail?id=270 Building protobuf 2.5.0 under Darwin (Mac OS X) was straight forward enough for me but getting it to build with the MATLAB extension was anything but easy. I didn't want to install Maven, yet another build system, we already have make, Ant, and Gradle, so I used Gradle to build it. The build downloads the source, configures it, and does the build. To get the MATLAB extension to build I had to patch some Makefiles which I probably didn't do a good job of but it is good enough. I've attached the Gradle build files and the Makefile patches I used. The reason I added this comment on this issue is because simplifying the Gradle build file, build.gradle, by removing the MATLAB support should be trivial. YMMV Attachments: protobuf-darwin-2.5.0.tgz 3.3 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Comment #9 on issue 270 by erdem...@gmail.com: Precompiled protoc binary for OS X https://code.google.com/p/protobuf/issues/detail?id=270 If you don't install Xcode and developer tools, you'll have to install the required dependencies on your own. Just for future reference, your configure output should be on OS X Yosem. with version protobuf-2.6.0; checking whether to enable maintainer-specific portions of Makefiles... yes checking build system type... x86_64-apple-darwin14.0.0 checking host system type... x86_64-apple-darwin14.0.0 checking target system type... x86_64-apple-darwin14.0.0 checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking C++ compiler flags.. use default: -O2 -g -DNDEBUG checking whether __SUNPRO_CC is declared... no checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld checking if the linker (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld) is GNU ld... no checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm checking the name lister (/usr/bin/nm) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 196608 checking whether the shell understands some XSI constructs... yes checking whether the shell understands +=... yes checking how to convert x86_64-apple-darwin14.0.0 file names to x86_64-apple-darwin14.0.0 format... func_convert_file_noop checking how to convert x86_64-apple-darwin14.0.0 file names to toolchain format... func_convert_file_noop checking for /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld option to reload object files... -r checking for objdump... no checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... no checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking for dsymutil... dsymutil checking for nmedit... nmedit checking for lipo... lipo checking for otool... otool checking for otool64... no checking for -single_module linker flag... yes checking for -exported_symbols_list linker flag... yes checking for -force_load linker flag... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... yes checking for gcc option to produce PIC... -fno-common -DPIC checking if gcc PIC flag -fno-common -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... darwin14.0.0 dyld checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build
[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Comment #8 on issue 270 by peter.on...@gmail.com: Precompiled protoc binary for OS X https://code.google.com/p/protobuf/issues/detail?id=270 Well, if you trust third party binary here it is: http://blog.ondruska.com/2014/11/google-protocol-buffers-compiler-binary.html -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Comment #6 on issue 270 by behrang@gmail.com: Precompiled protoc binary for OS X http://code.google.com/p/protobuf/issues/detail?id=270 For most of OS X developers brew is the tool so a brew formula should be good enough -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Updates: Status: WontFix Comment #5 on issue 270 by liuj...@google.com: Precompiled protoc binary for OS X http://code.google.com/p/protobuf/issues/detail?id=270 The mutex_ error was fixed in 2.4.1. Close this issue, as we will probably not provide a pre-compiled protoc for OSX at least in the near future. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Switching to a different machine with Snow Leopard and Xcode 4 did the trick for me. Thanks Inder On Thu, Apr 21, 2011 at 8:59 PM, Pherl Liu liuj...@google.com wrote: Also, you can upgrade your gcc to 4.3+ if possible. On Fri, Apr 22, 2011 at 11:58 AM, Pherl Liu liuj...@google.com wrote: This is due to the gcc 3.x bug. A workaround is submitted in svn r380. You can use svn head version, or patch the r380, or wait for the coming 2.4.1 release (soon). On Fri, Apr 22, 2011 at 2:19 AM, Inderjeet Singh inder...@gmail.com wrote: I have OSX 10.5 and Xcode 3 installed. I followed the following instructions from README.txt (for Unix systems): $ ./configure $ make make fails with the error I listed above. Are there instructions specific to Mac OS? Thanks Inder On Apr 20, 11:45 am, Peter Ondruska peter.ondru...@gmail.com wrote: I have OSX 10.6 and built with Xcode 3 and 4 with no problems. Did you readme.txt? -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
I have OSX 10.5 and Xcode 3 installed. I followed the following instructions from README.txt (for Unix systems): $ ./configure $ make make fails with the error I listed above. Are there instructions specific to Mac OS? Thanks Inder On Apr 20, 11:45 am, Peter Ondruska peter.ondru...@gmail.com wrote: I have OSX 10.6 and built with Xcode 3 and 4 with no problems. Did you readme.txt? -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
This is due to the gcc 3.x bug. A workaround is submitted in svn r380http://code.google.com/p/protobuf/source/detail?r=380. You can use svn head version, or patch the r380, or wait for the coming 2.4.1 release (soon). On Fri, Apr 22, 2011 at 2:19 AM, Inderjeet Singh inder...@gmail.com wrote: I have OSX 10.5 and Xcode 3 installed. I followed the following instructions from README.txt (for Unix systems): $ ./configure $ make make fails with the error I listed above. Are there instructions specific to Mac OS? Thanks Inder On Apr 20, 11:45 am, Peter Ondruska peter.ondru...@gmail.com wrote: I have OSX 10.6 and built with Xcode 3 and 4 with no problems. Did you readme.txt? -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Also, you can upgrade your gcc to 4.3+ if possible. On Fri, Apr 22, 2011 at 11:58 AM, Pherl Liu liuj...@google.com wrote: This is due to the gcc 3.x bug. A workaround is submitted in svn r380http://code.google.com/p/protobuf/source/detail?r=380. You can use svn head version, or patch the r380, or wait for the coming 2.4.1 release (soon). On Fri, Apr 22, 2011 at 2:19 AM, Inderjeet Singh inder...@gmail.comwrote: I have OSX 10.5 and Xcode 3 installed. I followed the following instructions from README.txt (for Unix systems): $ ./configure $ make make fails with the error I listed above. Are there instructions specific to Mac OS? Thanks Inder On Apr 20, 11:45 am, Peter Ondruska peter.ondru...@gmail.com wrote: I have OSX 10.6 and built with Xcode 3 and 4 with no problems. Did you readme.txt? -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Comment #4 on issue 270 by inder123: Precompiled protoc binary for OS X http://code.google.com/p/protobuf/issues/detail?id=270 I have XCode installed on my MacBook Pro (intel chip, fairly recent) with Leopard. However, make fails on me. Please consider providing precompiled Mac OS X binaries. dhcp-172-19-58-98:protobuf-2.4.0a inder$ make make all-recursive Making all in . Making all in src /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I..-D_THREAD_SAFE -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -O2 -g -DNDEBUG -MT descriptor.lo -MD -MP -MF .deps/descriptor.Tpo -c -o descriptor.lo `test -f 'google/protobuf/descriptor.cc' || echo './'`google/protobuf/descriptor.cc libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -D_THREAD_SAFE -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -O2 -g -DNDEBUG -MT descriptor.lo -MD -MP -MF .deps/descriptor.Tpo -c google/protobuf/descriptor.cc -o descriptor.o google/protobuf/descriptor.cc: In member function ‘virtual const google::protobuf::FieldDescriptor* google::protobuf::DescriptorBuilder::OptionInterpreter::AggregateOptionFinder::FindExtension(google::protobuf::Message*, const std::string) const’: ./google/protobuf/descriptor.h:1152: error: ‘google::protobuf::internal::Mutex* google::protobuf::DescriptorPool::mutex_’ is private google/protobuf/descriptor.cc:4341: error: within this context ./google/protobuf/descriptor.h:1152: error: ‘google::protobuf::internal::Mutex* google::protobuf::DescriptorPool::mutex_’ is private google/protobuf/descriptor.cc:4342: error: within this context make[2]: *** [descriptor.lo] Error 1 -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
I have OSX 10.6 and built with Xcode 3 and 4 with no problems. Did you readme.txt? -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Comment #1 on issue 270 by tempo...@gmail.com: Precompiled protoc binary for OS X http://code.google.com/p/protobuf/issues/detail?id=270 The main reason why we provide a precompiled binary on Windows is because obtaining and using development tools for Windows is relatively difficult. MSVC costs money, and Cygwin and MinGW are very different from what most Windows developers are used to. Linux is exactly the opposite. Practically every Linux user has a C++ compiler installed already, even if they don't actually know C++, so compiling from source is trivial. Meanwhile, if we wanted to provide a precompiled binary, we'd need to provide a different one for each distribution -- or provide a statically-linked one which would be enormous. OSX is somewhere in between. Xcode has to be installed, but it is free, and once you install it, building protoc from source is quite easy. Meanwhile, the mechanics of distributing binaries for Unix-style commands (as opposed to full-fledged Mac apps) in a way that will not have compatibility problems across versions of the OS is not entirely clear to me. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 270 in protobuf: Precompiled protoc binary for OS X
Comment #2 on issue 270 by peter.ge...@gmail.com: Precompiled protoc binary for OS X http://code.google.com/p/protobuf/issues/detail?id=270 thank you for the rapid response! so would a statically linked Mac binary be able to run on different versions of the OS? that sounds like exactly what i'm looking for. and when you say enormous, how big is that (XCode is a 3.5GB download!) is the windows binary not also statically linked? it's less than 2MB. per the README in the source distro, if i were to run ./configure --disable-shared would i get the precompiled binary i am looking for? -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
