- 01 Feb, 2019 1 commit
-
-
Paul Yang authored
* Use gnu for ruby build because strptime is provided by posix * Move option to extconf.rb * Remove unused code in Rakefile * Add config files for kokoro test * Use gnu 11 * Define _XOPEN_SOURCE * Add gnu11 option * Remove XOPEN * Try base_cc_flags * Try config_options * Move time.h to top * Try -D_XOPEN_SOURCE=700 * Define XOPEN_SOURCE directly * Try extconf.rb * Try CFLAGS * Try ext.cross_config_options * Make mac ruby release job fail on error * Try again * Try define _XOPEN_SOURCE in extconf.rb * Try again * Define __USE_XOPEN * Remove 2.6.0 * No mingw * Throw error on mingw * Remove XOPEN_SOURCE in upb * Add back mingw * Remove comment
-
- 23 Oct, 2018 1 commit
-
-
micw523 authored
-
- 25 Jun, 2018 1 commit
-
-
Paul Yang authored
* Install rake compiler * Add kokoro config to build ruby gem on linux * Rename from linix to linux * Fix prepare_build.sh name * Clean up * Install bundler * Install bundler * Use c99 in order to build gem on mingw-32 on ruby 2.0.0 See https://github.com/rake-compiler/rake-compiler-dock/issues/4 * Move c99 config to extcofig.rb
-
- 09 Mar, 2017 1 commit
-
-
Adam Cozzette authored
This commit adds a __wrap_memcpy function and a linker flag to use that in place of memcpy for our Ruby gem C extension. This allows us to always use the 2.2.5 version of memcpy, making it possible to use the gem on distributions with pre-2.14 versions of glibc. Before this change: $ objdump -T protobuf_c.so | grep memcpy 0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.4 __memcpy_chk 0000000000000000 DF *UND* 0000000000000000 GLIBC_2.14 memcpy After: $ objdump -T protobuf_c.so | grep memcpy 0000000000000000 DF *UND* 0000000000000000 GLIBC_2.2.5 memcpy 0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.4 __memcpy_chk 0000000000042450 g DF .text 0000000000000005 Base __wrap_memcpy This is based on gRPC's solution to a similar problem: https://github.com/grpc/grpc/blob/5098508d2d41a116113f7e333c516cd9ef34a943/src/core/lib/support/wrap_memcpy.c This fixes issue #2783.
-
- 09 Jun, 2015 2 commits
-
-
Josh Haberman authored
upb no longer requires -std=c99 but the Ruby/C code still uses C99 features.
-
Josh Haberman authored
Since this version of upb supports C89, all of the extra compiler flags are no longer required.
-
- 15 May, 2015 1 commit
-
-
Chris Fallin authored
- Alter encode/decode paths to use the `upb_env` (environment) abstraction. - Update upb amalgamation to upstream `93791bfe`. - Fix a compilation warning (void*->char* cast). - Modify build flags so that upb doesn't produce warnings -- the Travis build logs were pretty cluttered previously.
-
- 06 Jan, 2015 1 commit
-
-
Chris Fallin authored
This adds the Map container and support for parsing and serializing maps in the protobuf wire format (as defined by the C++ implementation, with MapEntry submessages in a repeated field). JSON map serialization/parsing are not yet supported as these will require some changes to upb as well.
-
- 12 Dec, 2014 1 commit
-
-
Chris Fallin authored
system. The Ruby module build now uses an amalgamated distribution of upb, and successfully builds a Ruby gem called 'google-protobuf' with module 'google/protobuf'.
-