[protobuf] building the protocol buffers with MinGW-4.4.0

[lucas_ro]

Hello,

Have anyone succeeded to build the protocol buffers using MinGW-4.4.0
under Windows ?

Thank you,
Florin

--

You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to proto...@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] building the protocol buffers with MinGW-4.4.0

[Kenton Varda]

Did you try and fail?  If so, please post the error log.

On Mon, Jan 4, 2010 at 5:52 AM, lucas_ro  wrote:

> Hello,
>
> Have anyone succeeded to build the protocol buffers using MinGW-4.4.0
> under Windows ?
>
> Thank you,
> Florin
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to proto...@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 proto...@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] Ivy Repository for protocol buffers binary

[Kenton Varda]

Does this have something to do with Maven?  If so, Greg (cc'd) would be the
person to ask.

On Fri, Jan 1, 2010 at 11:42 PM, Kay Kay  wrote:

> Would there be any site that already hosts the artifacts (of protocol
> buffers, - the jar files) in an ivy repository to be pulled from.
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to proto...@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 proto...@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] Ivy Repository for protocol buffers binary

[Gregory Kick]

I believe that Ivy lets you pull artifacts from a Maven repository.
That is probably the best way to go.

On Mon, Jan 4, 2010 at 10:09 AM, Kenton Varda  wrote:
> Does this have something to do with Maven?  If so, Greg (cc'd) would be the
> person to ask.
>
> On Fri, Jan 1, 2010 at 11:42 PM, Kay Kay  wrote:
>>
>> Would there be any site that already hosts the artifacts (of protocol
>> buffers, - the jar files) in an ivy repository to be pulled from.
>>
>> --
>>
>> You received this message because you are subscribed to the Google Groups
>> "Protocol Buffers" group.
>> To post to this group, send email to proto...@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.
>>
>>
>
>



-- 
Greg Kick
Data Liberation & Feedburner

--

You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to proto...@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: building the protocol buffers with MinGW-4.4.0

[lucas_ro]

Eventually I succeeded by changing in the file  libstdc++.la the value
of the variable library_names from 'libstdc++.dll.a' to 'libstdc++.a'.
The libtool was complaining about the missing of the file 'libstdc+
+.dll.a'. It seems that this is a mingw-4.4.0 known issue.

Also I choose to build only the static library (passing the option --
disable-shared on to the command 'configure').


On Jan 4, 8:07 pm, Kenton Varda  wrote:
> Did you try and fail?  If so, please post the error log.
>
>
>
> On Mon, Jan 4, 2010 at 5:52 AM, lucas_ro  wrote:
> > Hello,
>
> > Have anyone succeeded to build the protocol buffers using MinGW-4.4.0
> > under Windows ?
>
> > Thank you,
> > Florin
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Protocol Buffers" group.
> > To post to this group, send email to proto...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > protobuf+unsubscr...@googlegroups.com > om>
> > .
> > 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 proto...@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: building the protocol buffers with MinGW-4.4.0

[Kenton Varda]

I see.  Is mingw-4.4.0 a stable release or a beta?  Unfortunately their web
site is pretty terribly designed and I cannot figure this out.  If it's an
official release then we should probably work around the bug, but otherwise
I assume they'll fix it since it's a known issue.

On Mon, Jan 4, 2010 at 11:07 AM, lucas_ro  wrote:

> Eventually I succeeded by changing in the file  libstdc++.la the value
> of the variable library_names from 'libstdc++.dll.a' to 'libstdc++.a'.
> The libtool was complaining about the missing of the file 'libstdc+
> +.dll.a'. It seems that this is a mingw-4.4.0 known issue.
>
> Also I choose to build only the static library (passing the option --
> disable-shared on to the command 'configure').
>
>
> On Jan 4, 8:07 pm, Kenton Varda  wrote:
> > Did you try and fail?  If so, please post the error log.
> >
> >
> >
> > On Mon, Jan 4, 2010 at 5:52 AM, lucas_ro  wrote:
> > > Hello,
> >
> > > Have anyone succeeded to build the protocol buffers using MinGW-4.4.0
> > > under Windows ?
> >
> > > Thank you,
> > > Florin
> >
> > > --
> >
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Protocol Buffers" group.
> > > To post to this group, send email to proto...@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 proto...@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 proto...@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: building the protocol buffers with MinGW-4.4.0

[lucas_ro]

It's the official stable release. As I observed by searching the web
for a solution the issue regarding 'libstdc++.dll.a' is well known.
Unfortunately it seems that they (mingw team) react very slowly in
fixing the signaled issues/bugs.

The link that helped me is 
http://eschew.wordpress.com/2009/09/20/building-protobuf-with-mingw-gcc-4-4-0/.
(however it is not necessary to install the mozilla-build tree).

On Jan 4, 9:27 pm, Kenton Varda  wrote:
> I see.  Is mingw-4.4.0 a stable release or a beta?  Unfortunately their web
> site is pretty terribly designed and I cannot figure this out.  If it's an
> official release then we should probably work around the bug, but otherwise
> I assume they'll fix it since it's a known issue.
>
>
>
> On Mon, Jan 4, 2010 at 11:07 AM, lucas_ro  wrote:
> > Eventually I succeeded by changing in the file  libstdc++.la the value
> > of the variable library_names from 'libstdc++.dll.a' to 'libstdc++.a'.
> > The libtool was complaining about the missing of the file 'libstdc+
> > +.dll.a'. It seems that this is a mingw-4.4.0 known issue.
>
> > Also I choose to build only the static library (passing the option --
> > disable-shared on to the command 'configure').
>
> > On Jan 4, 8:07 pm, Kenton Varda  wrote:
> > > Did you try and fail?  If so, please post the error log.
>
> > > On Mon, Jan 4, 2010 at 5:52 AM, lucas_ro  wrote:
> > > > Hello,
>
> > > > Have anyone succeeded to build the protocol buffers using MinGW-4.4.0
> > > > under Windows ?
>
> > > > Thank you,
> > > > Florin
>
> > > > --
>
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "Protocol Buffers" group.
> > > > To post to this group, send email to proto...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > protobuf+unsubscr...@googlegroups.com > > >  om>
> > 
> > > > .
> > > > 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 proto...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > protobuf+unsubscr...@googlegroups.com > om>
> > .
> > 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 proto...@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: WriteDelimited/parseDelimited in python

[Kenton Varda]

Mostly looks good.  There are some style issues (e.g. lines over 80 chars)
but I can clean those up myself.

You'll need to sign the contributor license agreement:

http://code.google.com/legal/individual-cla-v1.0.html -- If you own
copyright on this change.
http://code.google.com/legal/corporate-cla-v1.0.html -- If your employer
does.

Please let me know after you've done this and then I can submit these.
 
On Fri, Jan 1, 2010 at 12:53 PM, Graham  wrote:

> On Jan 1, 7:32 am, Kenton Varda  wrote:
> > I don't think an equivalent has been added to the Python API.  Want to
> write
> > up a patch?
>
> Well - if you insist... Here's a first run, which seems to work but
> I'm a very long way from a competent python programmers so feel free
> to fix it up some :)
>
> I can't see how to attach files using the google groups interface, so
> I've stuck them on my webspace for now:
> http://grahamcox.co.uk/patches/protobuf/
> There's two patches - one for serializing in a delimited form, and one
> for deserializing from a delimited form.
> --
> Graham Cox
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to proto...@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 proto...@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: Windows Dll

[Kenton Varda]

Fixed in revision 286.

On Fri, Dec 25, 2009 at 2:28 PM, Kenton Varda  wrote:

> Ah, yeah, I hadn't tested compiling as a DLL under MSVC yet.  Thanks for
> reminding me to fix this before the final release.  2.2.0 should work.
>
>
> On Fri, Dec 25, 2009 at 1:27 AM, Soth  wrote:
>
>> I`m using 2.3.0rc1.
>>
>> On 25 дек, 07:07, Kenton Varda  wrote:
>> > What version did you try this with?
>> >
>> > On Thu, Dec 24, 2009 at 3:38 PM, Soth  wrote:
>> > > Hi,
>> > > I`ve tried to compile the protocol buffers library as a DLL in
>> > > msvs2008 and it didn`t link. The problems are basically with incorrect
>> > > export of functions/classes from the libprotobuf-lite and
>> > > libprotobuf :
>> >
>> > > 1) StringSpaceUsedExcludingSelf undefined in lite, to solve moved
>> > > definition from generated_message_reflection.h to repeated_field.cc
>> >
>> > > 2) bool DescriptorPoolExtensionFinder::Find(int number, ExtensionInfo*
>> > > output) undefined in lite and i think it can be only solved by
>> > > removing DescriptorPoolExtensionFinder class declaration from the
>> > > extension_set.h and placing it in to a new file in libprotobuf
>> > > extension_set_heavy.h or somewhere else in libprotobuf local headers.
>> >
>> > > On Dec 23, 3:51 am, Kenton Varda  wrote:
>> > > > If you link protobuf as a DLL:
>> >
>> > > > (1) You must link to the C runtime as a DLL, otherwise you'll end up
>> with
>> > > > two copies of the C runtime, which may mean two separate heaps,
>> among
>> > > other
>> > > > things.
>> >
>> > > > (2) All components of your application which use protocol buffers
>> must
>> > > link
>> > > > to the same C runtime as the protocol buffers DLL.  This is true
>> when
>> > > static
>> > > > linking as well, but sometimes people mistakenly think that it is
>> not
>> > > true
>> > > > with DLLs.
>> >
>> > > > (3) All components of your application which use protocol buffers
>> must
>> > > use
>> > > > the same version of protocol buffers.  The DLL binary interface is
>> not
>> > > > compatible between two different versions.
>> >
>> > > > (4) You absolutely cannot place the protobuf DLL in a system shared
>> > > > directory, because it may be incompatible with other apps which use
>> a
>> > > > different version of the DLL.  The DLL has to stay in your
>> application's
>> > > own
>> > > > directory.
>> >
>> > > > Given these constraints, there isn't much benefit to dynamic linking
>> for
>> > > > most people.  Usually the advantage of using a DLL is that you can
>> share
>> > > it
>> > > > between multiple programs, but that is unlikely to work well with
>> > > protocol
>> > > > buffers due to the interface version compatibility issues.
>> >
>> > > > Another typical reason to use DLLs is because you want to provide a
>> > > "plugin"
>> > > > system for your application.  But if all your plugins link against
>> > > > libprotobuf as a DLL, then they must all use the same version of
>> protocol
>> > > > buffers, which is a pretty serious limitation to any plugin system.
>>  A
>> > > > better approach would be to statically link each plugin individually
>> > > against
>> > > > protocol buffers; this way, each plugin has its own embedded copy
>> and
>> > > > doesn't have to worry about version compatibility with other
>> plugins.
>> > > >  However, if you do this, then you cannot pass protocol buffer
>> objects
>> > > > between plugins, since they might use different versions of the
>> library.
>> > > You
>> > > > can, however, pass encoded messages between plugins -- the encoding
>> > > format
>> > > > is (obviously) compatible between versions.
>> >
>> > > > On Mon, Dec 21, 2009 at 5:21 PM, Soth  wrote:
>> > > > > Hi,
>> > > > > in protobuf documentation it`s stated that static linking is
>> preferred
>> > > > > to dynamic because of different issues. I`d like to know what
>> these
>> > > > > issues are, what i shouldnt do with the protobuf if i link with it
>> > > > > dynamically and how come that static linking is better. Thanks
>> ahead.
>> >
>> > > > > --
>> >
>> > > > > You received this message because you are subscribed to the Google
>> > > Groups
>> > > > > "Protocol Buffers" group.
>> > > > > To post to this group, send email to proto...@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.-Hide quoted text -
>> >
>> > > > - Show quoted text -
>> >
>> > > --
>> >
>> > > You received this message because you are subscribed to the Google
>> Groups
>> > > "Protocol Buffers" group.
>> > > To post to this group, send email to proto...@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 beca

Re: [protobuf] Re: WriteDelimited/parseDelimited in python

[Kenton Varda]

Hmm, it occurs to me that this currently is not useful for reading from a
socket or similar stream since the caller has to make sure to read an entire
message before trying to parse it, but the caller doesn't actually know how
long the message is (because the code that determines this is encapsulated).
 Any thoughts on this?

On Mon, Jan 4, 2010 at 12:11 PM, Kenton Varda  wrote:

> Mostly looks good.  There are some style issues (e.g. lines over 80 chars)
> but I can clean those up myself.
>
> You'll need to sign the contributor license agreement:
>
> http://code.google.com/legal/individual-cla-v1.0.html -- If you own
> copyright on this change.
> http://code.google.com/legal/corporate-cla-v1.0.html -- If your employer
> does.
>
> Please let me know after you've done this and then I can submit these.
>
>  
> On Fri, Jan 1, 2010 at 12:53 PM, Graham  wrote:
>
>> On Jan 1, 7:32 am, Kenton Varda  wrote:
>> > I don't think an equivalent has been added to the Python API.  Want to
>> write
>> > up a patch?
>>
>> Well - if you insist... Here's a first run, which seems to work but
>> I'm a very long way from a competent python programmers so feel free
>> to fix it up some :)
>>
>> I can't see how to attach files using the google groups interface, so
>> I've stuck them on my webspace for now:
>> http://grahamcox.co.uk/patches/protobuf/
>> There's two patches - one for serializing in a delimited form, and one
>> for deserializing from a delimited form.
>> --
>> Graham Cox
>>
>> --
>>
>> You received this message because you are subscribed to the Google Groups
>> "Protocol Buffers" group.
>> To post to this group, send email to proto...@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 proto...@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] javascript protocol buffers encoder

[alf]

There are any away to encode data to protobuffer message directly from
javascript ?

what do you think about this idea. load data,
encode,
convert to string,
send to server,
receive to serve,
convert string to bytes,
decode to pb message

any opensource tools.

many thanks.



--

You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to proto...@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] javascript protocol buffers encoder

[Kenton Varda]

Two problems with encoding/decoding binary messages in javascript:
- Javascript doesn't have a usable "array of bytes" type.
- Even if it did, encoding/decoding would be painfully slow and would
require downloading a lot of code to the client.

A better idea is to encode messages in JSON format.  There's at least one
(third-party) JSON codec for protocol buffers here:

http://code.google.com/p/protobuf-java-format/

It's easy to write your own JSON codec against any of the official protobuf
implementations using the reflection interfaces.  Look at how TextFormat is
implemented in each language for an example.

On Mon, Jan 4, 2010 at 2:30 PM, alf  wrote:

> There are any away to encode data to protobuffer message directly from
> javascript ?
>
> what do you think about this idea. load data,
> encode,
> convert to string,
> send to server,
> receive to serve,
> convert string to bytes,
> decode to pb message
>
> any opensource tools.
>
> many thanks.
>
>
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to proto...@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 proto...@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: WriteDelimited/parseDelimited in python

[Kenton Varda]

Make sure to "reply all" so that the group is CC'd.

So you are saying that the user should read whatever data is on the socket,
then attempt to parse it, and if it fails, assume that it's because there is
more data to read?  Seems rather wasteful.  I think what we ideally want is
either:
(a) Provide a way for the caller to read the size independently, so that
they can then make sure to read that many bytes from the input before
parsing.
(b) Provide a method that reads from a stream, so that the protobuf library
can automatically take care of reading all necessary bytes.

Option (b) is obviously cleaner but has a few problems:
- We have to choose a particular stream interface to support.  While the
Python "file-like" interface is pretty common I'm not sure if it's universal
for this kind of task.
- If not all bytes of the message are available yet, we'd have to block.
 This might be fine most of the time, but would be unacceptable for some
uses.

Thoughts?

On Mon, Jan 4, 2010 at 3:09 PM, Graham Cox  wrote:

> I'm using it for reading/writing to sockets in my functional tests - works
> well enough there...
> In my Java-side server code, I read from the socket into a byte buffer,
> then deserialize the byte buffer into Protobuf objects, throwing away the
> data that has been deserialized. The python "MergeDelimitedFromString"
> function also returns the number of bytes that were processed to build up
> the Protobuf object, so the user could easily do the same - read the socket
> onto the end of a buffer, and then while the buffer is successfully
> deserializing into objects throw away the first x bytes as appropriate...
>
> Just a thought :)
>
> On Mon, Jan 4, 2010 at 9:57 PM, Kenton Varda  wrote:
>
>> Hmm, it occurs to me that this currently is not useful for reading from a
>> socket or similar stream since the caller has to make sure to read an entire
>> message before trying to parse it, but the caller doesn't actually know how
>> long the message is (because the code that determines this is encapsulated).
>>  Any thoughts on this?
>>
>> On Mon, Jan 4, 2010 at 12:11 PM, Kenton Varda  wrote:
>>
>>> Mostly looks good.  There are some style issues (e.g. lines over 80
>>> chars) but I can clean those up myself.
>>>
>>> You'll need to sign the contributor license agreement:
>>>
>>> http://code.google.com/legal/individual-cla-v1.0.html -- If you own
>>> copyright on this change.
>>> http://code.google.com/legal/corporate-cla-v1.0.html -- If your employer
>>> does.
>>>
>>> Please let me know after you've done this and then I can submit these.
>>>
>>>
>>> On Fri, Jan 1, 2010 at 12:53 PM, Graham  wrote:
>>>
 On Jan 1, 7:32 am, Kenton Varda  wrote:
 > I don't think an equivalent has been added to the Python API.  Want to
 write
 > up a patch?

 Well - if you insist... Here's a first run, which seems to work but
 I'm a very long way from a competent python programmers so feel free
 to fix it up some :)

 I can't see how to attach files using the google groups interface, so
 I've stuck them on my webspace for now:
 http://grahamcox.co.uk/patches/protobuf/
 There's two patches - one for serializing in a delimited form, and one
 for deserializing from a delimited form.
 --
 Graham Cox

 --

 You received this message because you are subscribed to the Google
 Groups "Protocol Buffers" group.
 To post to this group, send email to proto...@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 proto...@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: building the protocol buffers with MinGW-4.4.0

[Kenton Varda]

OK, I'm pretty confused now.  Apparently there is a MinGW 5.1.6.  However,
the MinGW version number does not appear to be related to the GCC version
number -- it comes with gcc 3.4.5.  Your link talks about building with
MinGW and *GCC* 4.4.0.  Last I knew, MinGW had not yet provided an official
release with GCC 4.x and AFAICT this is still the case.

During the install I chose the "current" release.  Maybe you chose the
"candidate"?

On Mon, Jan 4, 2010 at 12:02 PM, lucas_ro  wrote:

> It's the official stable release. As I observed by searching the web
> for a solution the issue regarding 'libstdc++.dll.a' is well known.
> Unfortunately it seems that they (mingw team) react very slowly in
> fixing the signaled issues/bugs.
>
> The link that helped me is
> http://eschew.wordpress.com/2009/09/20/building-protobuf-with-mingw-gcc-4-4-0/
> .
> (however it is not necessary to install the mozilla-build tree).
>
> On Jan 4, 9:27 pm, Kenton Varda  wrote:
> > I see.  Is mingw-4.4.0 a stable release or a beta?  Unfortunately their
> web
> > site is pretty terribly designed and I cannot figure this out.  If it's
> an
> > official release then we should probably work around the bug, but
> otherwise
> > I assume they'll fix it since it's a known issue.
> >
> >
> >
> > On Mon, Jan 4, 2010 at 11:07 AM, lucas_ro  wrote:
> > > Eventually I succeeded by changing in the file  libstdc++.la the value
> > > of the variable library_names from 'libstdc++.dll.a' to 'libstdc++.a'.
> > > The libtool was complaining about the missing of the file 'libstdc+
> > > +.dll.a'. It seems that this is a mingw-4.4.0 known issue.
> >
> > > Also I choose to build only the static library (passing the option --
> > > disable-shared on to the command 'configure').
> >
> > > On Jan 4, 8:07 pm, Kenton Varda  wrote:
> > > > Did you try and fail?  If so, please post the error log.
> >
> > > > On Mon, Jan 4, 2010 at 5:52 AM, lucas_ro 
> wrote:
> > > > > Hello,
> >
> > > > > Have anyone succeeded to build the protocol buffers using
> MinGW-4.4.0
> > > > > under Windows ?
> >
> > > > > Thank you,
> > > > > Florin
> >
> > > > > --
> >
> > > > > You received this message because you are subscribed to the Google
> > > Groups
> > > > > "Protocol Buffers" group.
> > > > > To post to this group, send email to proto...@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 proto...@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 proto...@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 proto...@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: building the protocol buffers with MinGW-4.4.0

[lucas_ro]

Ok, I try to make the stuffs more clear.

In order to get the official MinGW 4.4.0 (aka gcc 4.4.0) you have to
follow the link http://sourceforge.net/projects/mingw/files/. Downward
that page please look for GCC Version 4 then expand it and find out
CurrentRelease_gcc-4.4.0. Under the latter branch you may find the
official release of gcc 4.4.0 for Windows. Please read the content of
the file gcc-4.4.0-mingw-notes.txt in order to have some hints on the
installation of this software package.

If you find the above procedure too complicated (and indeed it is)
then the simplest way to have MinGW-4.4.0 is to download the following
file: ftp://ftp.qt.nokia.com/misc/MinGW-gcc440_1.zip . It is the
official release patched in order to allow the building of the
DirectShow under MinGW.

The executable MinGW 5.1.6 installs the version 3.4.5 of gcc !!!

On Jan 5, 4:38 am, Kenton Varda  wrote:
> OK, I'm pretty confused now.  Apparently there is a MinGW 5.1.6.  However,
> the MinGW version number does not appear to be related to the GCC version
> number -- it comes with gcc 3.4.5.  Your link talks about building with
> MinGW and *GCC* 4.4.0.  Last I knew, MinGW had not yet provided an official
> release with GCC 4.x and AFAICT this is still the case.
>
> During the install I chose the "current" release.  Maybe you chose the
> "candidate"?
>
>
>
> On Mon, Jan 4, 2010 at 12:02 PM, lucas_ro  wrote:
> > It's the official stable release. As I observed by searching the web
> > for a solution the issue regarding 'libstdc++.dll.a' is well known.
> > Unfortunately it seems that they (mingw team) react very slowly in
> > fixing the signaled issues/bugs.
>
> > The link that helped me is
> >http://eschew.wordpress.com/2009/09/20/building-protobuf-with-mingw-g...
> > .
> > (however it is not necessary to install the mozilla-build tree).
>
> > On Jan 4, 9:27 pm, Kenton Varda  wrote:
> > > I see.  Is mingw-4.4.0 a stable release or a beta?  Unfortunately their
> > web
> > > site is pretty terribly designed and I cannot figure this out.  If it's
> > an
> > > official release then we should probably work around the bug, but
> > otherwise
> > > I assume they'll fix it since it's a known issue.
>
> > > On Mon, Jan 4, 2010 at 11:07 AM, lucas_ro  wrote:
> > > > Eventually I succeeded by changing in the file  libstdc++.la the value
> > > > of the variable library_names from 'libstdc++.dll.a' to 'libstdc++.a'.
> > > > The libtool was complaining about the missing of the file 'libstdc+
> > > > +.dll.a'. It seems that this is a mingw-4.4.0 known issue.
>
> > > > Also I choose to build only the static library (passing the option --
> > > > disable-shared on to the command 'configure').
>
> > > > On Jan 4, 8:07 pm, Kenton Varda  wrote:
> > > > > Did you try and fail?  If so, please post the error log.
>
> > > > > On Mon, Jan 4, 2010 at 5:52 AM, lucas_ro 
> > wrote:
> > > > > > Hello,
>
> > > > > > Have anyone succeeded to build the protocol buffers using
> > MinGW-4.4.0
> > > > > > under Windows ?
>
> > > > > > Thank you,
> > > > > > Florin
>
> > > > > > --
>
> > > > > > You received this message because you are subscribed to the Google
> > > > Groups
> > > > > > "Protocol Buffers" group.
> > > > > > To post to this group, send email to proto...@googlegroups.com.
> > > > > > To unsubscribe from this group, send email to
> > > > > > protobuf+unsubscr...@googlegroups.com > > > > >  om>
> > 
> > > > 
> > > > > > .
> > > > > > 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 proto...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > protobuf+unsubscr...@googlegroups.com > > >  om>
> > 
> > > > .
> > > > 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 proto...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > protobuf+unsubscr...@googlegroups.com > om>
> > .
> > 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 proto...@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.