Is there any concrete plan to add mercurial support to depot_tools? It
sounds like the kind of thing that will not happen until someone needs it.
But if no one switches to mercurial then there will never be a need. So
unless there is a reasonable target date set for this support, I think we
shou
Will it still work with depot_tools? I use gclient with several projects, it
is just awesome. AFAIK, it does not support mercurial yet. Please, consider
this use case before doing the change.
On Thu, Apr 1, 2010 at 5:37 PM, Kenton Varda wrote:
> <3 Mercurial
>
> (I plan to switch protobufs to it
Comment #6 on issue 177 by ken...@google.com: undefined symbol in shared
lib on Ubuntu 10.04
http://code.google.com/p/protobuf/issues/detail?id=177
Note that you can use the "strip" command to remove unnecessary debug
symbols and
other stuff from the binary, which may make it significantly
Strange, this is the first I've heard of this problem affecting C++.
Can you possibly split your .proto into multiple files? It takes quite a
monster of a file to produce a 64k descriptor, even when using lots of
custom options. It seems like such a file would be hard to maintain anyway,
so spli
You can download and install pkg-config pretty easily.
Typically the only flags needed to link against libprotobuf are -lprotobuf,
-lz, and whatever flags are required by pthreads on your system. No cflags
are required unless your headers were installed somewhere unusual (but you
might want -pthr
Sorry, I meant all the python source code files without "test" in the name.
You do not need any of the C++ or Java stuff if you are only using Python in
production.
On Wed, Apr 7, 2010 at 3:29 PM, Sherry Yang wrote:
> Kenton,
> Thanks for the followup. I actually copied over the complete inst
It looks like you just copied over the source code. You need to install the
modules in a place where python can find them: the python/setup.py script
does this for you.
On Wed, Apr 7, 2010 at 3:29 PM, Sherry Yang wrote:
> Kenton,
> Thanks for the followup. I actually copied over the complete i
Kenton,
Thanks for the followup. I actually copied over the complete install to
the production server and this did not help. Here are the directories (and
their subdirectories) I copied:
protobuf-2.3.0]$ ls
aclocal.m4config.status editors libtool
protobuf-lite.pc
You need all the files that don't have "test" in the name. (The test files
shouldn't be installed anyway.)
Protobufs do not depend on anything outside the Python standard library.
On Wed, Apr 7, 2010 at 2:01 PM, Eric wrote:
> Hello,
> I have Python and Google Protocol Buffers running on a Cen
Hello,
I have Python and Google Protocol Buffers running on a CentOS system
using the standard install. I want to run my Python scripts on a
production server (also CentOS) but if possible I would like avoid
doing the full install. Is there a relatively small subset of files I
can copy from the d
Jason,
Thanks for the ideas. setuptools failed to install because zlib was not
installed. I installed zlib and it still failed so I reinstalled python
(after the zlib install) and everything works now.
thanks again!
Eric
On Wed, Apr 7, 2010 at 11:51 AM, Jason Hsueh wrote:
> (Adding the group
Kenton, do you have any experience compiling protobufs on OSX?
On Wed, Apr 7, 2010 at 9:34 AM, Romain Francois <
romain.francois.r.enthusi...@gmail.com> wrote:
> Hello,
>
> Please bear with me if this is obvious ... I'm new to OSX.
>
> Are there instructions somewhere to build protobuf for both i
Updates:
Status: WorkingAsIntended
Owner: jas...@google.com
Comment #5 on issue 177 by jas...@google.com: undefined symbol in shared
lib on Ubuntu 10.04
http://code.google.com/p/protobuf/issues/detail?id=177
(No comment was entered for this change.)
--
You received this messa
What error do you get when trying to use the generated class? With python
2.5.2 I was able to execute the sample add_person.py program.
On Wed, Apr 7, 2010 at 11:27 AM, dear chap wrote:
> I have this weird problem when generating python files from .proto
> files using protoc. I am running protoc
(Adding the group back to the discussion)
pkg_resources should be part of setuptools, which should be installed as
part of running the setup.py script. From the python README:
2) If you do not have setuptools installed, note that it will be
downloaded and installed automatically as soon as you
I have this weird problem when generating python files from .proto
files using protoc. I am running protoc on addressbook.proto
and in the addressbook_pb2.py I have this string
DESCRIPTOR = descriptor.FileDescriptor(
name='addressbook.proto',
package='tutorial',
serialized_pb='\n\x11\x61\x64
Hello,
Please bear with me if this is obvious ... I'm new to OSX.
Are there instructions somewhere to build protobuf for both i386 and
x86_64 architectures on OSX.
Also, on linux I can do :
$ pkg-config --libs protobuf
$ pkg-config --cflags protobuf
but OSX does not have pkg-config. I can
The problem seems to occur with Visual C++ 2008 also. The test project
compiled succesfully before because I had accidentally left the
exampleenum.pb.cc and enumextension.pb.cc files out from the solution.
On 7 huhti, 00:48, Jason Hsueh wrote:
> This sounds like a C++ version of the Java issue
18 matches
Mail list logo
