fast_excel 0.1.4 → 0.1.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5b3fea677b83c37195affe038f16bcc03cad62a0
-  data.tar.gz: 91383abc260bb5df19bf9153efcd53f4d1e3fd43
+  metadata.gz: 5fea186d154ccc93b112e497f6d2eb19f6f1471c
+  data.tar.gz: f2a918430b64e7fe453e48b11e18fcf72cf105a7
 SHA512:
-  metadata.gz: 83b36430c0c230863a9659790932a39c4e670d7e0b8c687a8f26ce82998d4f362a201d07ef9bbcbedae9725e66156a5d1ea37db3b9c390b51bdd69e35f295668
-  data.tar.gz: 0ffe702bfd23a34bcd75e3b33d63629928acf8ca2da407a06262d16c40ca4a0ca75846483ca0cf8dff5438832ba18380a0dbef859338def57e1d836445e1ef4b
+  metadata.gz: 5d3d835819ec9dcff29dfec369535e16af37cf5b2627c16508b4ca6242c629a7ee407682e729a00f541a775af4b85fea4344c82ca2a5d8ba41ac3be3f5d180a9
+  data.tar.gz: 3c83478ba13197ee50be02c29c5af4c694a1c72da2ee0120d1f9e8cb667ff095850bca22200ca42746cd5fe7c00a4050102dd2f2cb38ebfe28be4808958f0e11

data/.gitignore

@@ -1,4 +1,3 @@
-libxlsxwriter
 .ruby-version
 try.c
 try.rb
@@ -7,4 +6,8 @@ gen_ffi.rb
 *.xlsx
 a.out
 .DS_Store
-*.gem
+*.gem
+libxlsxwriter/dev
+libxlsxwriter/docs
+libxlsxwriter/examples
+libxlsxwriter/test

data/Makefile

@@ -0,0 +1,14 @@
+Q=@
+ifdef V
+Q=
+endif
+
+all :
+	@echo "Compiling libxlsxwriter ..."
+	$(Q)$(MAKE) -C libxlsxwriter
+
+clean :
+	#$(Q)$(MAKE) clean -C libxlsxwriter
+
+install :
+	@echo "Nothing to install"

data/README.md

@@ -2,7 +2,12 @@
 
 ```ruby
 workbook = FastExcel.open("hello_world_ffi.xlsx", constant_memory: true)
-worksheet = workbook.add_worksheet("Garuda Payments")
+workbook.default_format.set(
+  font_size: 0, # user's default
+  font_family: "Arial"
+)
+
+worksheet = workbook.add_worksheet("Example Report")
 
 bold = workbook.bold_cell_format
 worksheet.set_column(0, 0, FastExcel::DEF_COL_WIDTH, bold)
@@ -34,5 +39,5 @@ end
 workbook.close
 ```
 
-This repositiry and gem contain precompiled [libxlsxwriter](https://github.com/jmcnamara/libxlsxwriter) for MacOs, Linux with glibc and Alpine Linux
+This repositiry and gem contain sources of [libxlsxwriter](https://github.com/jmcnamara/libxlsxwriter)
 

data/Rakefile

@@ -24,4 +24,14 @@ namespace :build do
     system("docker cp #{last_container_id}:/srv/libxlsxwriter/lib/libxlsxwriter.so ./binaries/libxlsxwriter-alpine.so")
     system("docker rm #{last_container_id}")
   end
+end
+
+task :sync do
+  require 'fileutils'
+  FileUtils.rm_rf("./libxlsxwriter")
+  system("git clone --depth 10 git@github.com:Paxa/libxlsxwriter.git")
+  Dir.chdir("./libxlsxwriter") do
+    system("git show --pretty='format:%cd %h' --date=iso --quiet > version.txt")
+    FileUtils.rm_rf("./.git")
+  end
 end

data/fast_excel.gemspec

@@ -1,18 +1,20 @@
 Gem::Specification.new do |s|
   s.name        = "fast_excel"
-  s.version     = "0.1.4"
+  s.version     = "0.1.5"
   s.author      = ["Pavel Evstigneev"]
   s.email       = ["pavel.evst@gmail.com"]
   s.homepage    = "https://github.com/paxa/fast_excel"
   s.summary     = %q{Ultra Fast Excel Writter}
   s.description = "Wrapper for libxlsxwriter using ffi"
   s.license     = 'MIT'
+  s.has_rdoc    = false
   s.required_ruby_version = '~> 2.0'
 
   s.files       = `git ls-files`.split("\n")
   s.test_files  = []
 
   s.require_paths = ["lib"]
+  s.extensions = ["extconf.rb"]
 
   s.add_runtime_dependency "ffi", ["> 1.9", "< 2"]
 end

data/lib/fast_excel/binding.rb

@@ -6,16 +6,12 @@ module Libxlsxwriter
   extend FFI::Library
 
   LIB_FILENAME = if RUBY_PLATFORM =~ /darwin/
-    "libxlsxwriter-darwin.dylib"
+    "libxlsxwriter.dylib"
   else
-    if File.exist?('/etc/alpine-release')
-      "libxlsxwriter-alpine.so"
-    else
-      "libxlsxwriter-glibc.so"
-    end
+    "libxlsxwriter.so"
   end
 
-  ffi_lib File.expand_path("./../../../binaries/#{LIB_FILENAME}", __FILE__)
+  ffi_lib File.expand_path("./../../../libxlsxwriter/lib/#{LIB_FILENAME}", __FILE__)
 
   def self.attach_function(name, *_)
     begin; super; rescue FFI::NotFoundError => e

data/lib/rubygems_plugin.rb

@@ -0,0 +1,3 @@
+Gem.post_install do |installer|
+  puts "Post install message"
+end

data/libxlsxwriter/.gitignore

@@ -0,0 +1,49 @@
+*.a
+*.o
+*.so
+*.to
+*.lo
+*.la
+*.dylib
+*.dll
+test_*
+!test_*.c
+!test_*.cpp
+!test_*.py
+*.tar.gz
+*~
+TAGS
+.#*
+*#
+~*xlsx
+*.xlsx
+*.bak
+!test/functional/xlsx_files/*.xlsx
+*.pyc
+.cproject
+.project
+.pydevproject
+.settings/
+.DS_Store
+__pycache__
+.cache
+docs/html
+docs/latex
+.deps
+.dirstamp
+_temp.c
+examples/*
+!examples/*.c
+!examples/logo.png
+!examples/Makefile
+cov-int
+libxlsxwriter-coverity.tgz
+
+third_party/zlib-1.2.8/configure.log
+third_party/zlib-1.2.8/contrib/minizip/miniunz
+third_party/zlib-1.2.8/contrib/minizip/minizip
+third_party/zlib-1.2.8/example
+third_party/zlib-1.2.8/examplesh
+third_party/zlib-1.2.8/minigzip
+third_party/zlib-1.2.8/minigzipsh
+third_party/zlib-1.2.8/zlib.pc

data/libxlsxwriter/.indent.pro

@@ -0,0 +1,125 @@
+/*
+ * Indent rules for libxlsxwriter.
+ *
+ * The rules for user defined typedefs can be update as follows:
+ *
+   perl -i -pe 'print and last if /[l]ibxlsxwriter typedefs/' .indent.pro
+   ack -h typedef include/xlsxwriter/*.h src/*.c | perl -lne 'print "-T $1" if /\w+\s+\w+\s+(\w+)/' | sort >> .indent.pro
+ *
+ */
+
+/* Command line options used with GNU indent 2.2.10 */
+--braces-on-if-line
+--braces-on-struct-decl-line
+--case-indentation 4
+--continue-at-parentheses
+--declaration-comment-column 0
+--format-first-column-comments
+--honour-newlines
+--ignore-profile
+--indent-label 0
+--indent-level 4
+--no-space-after-function-call-names
+--no-tabs
+--swallow-optional-blank-lines
+
+/* Typedefs used in the code. */
+-T int8_t
+-T int16_t
+-T int32_t
+-T int64_t
+-T uint8_t
+-T uint16_t
+-T uint32_t
+-T uint64_t
+-T ssize_t
+-T size_t
+-T time_t
+
+-T LIST_ENTRY
+-T RB_ENTRY
+-T SLIST_ENTRY
+-T STAILQ_ENTRY
+-T TAILQ_ENTRY
+
+/* libxlsxwriter typedefs. */
+-T lxw_app
+-T lxw_autofilter
+-T lxw_border
+-T lxw_cell
+-T lxw_chart
+-T lxw_chart_axis
+-T lxw_chart_axis_display_unit
+-T lxw_chart_axis_label_position
+-T lxw_chart_axis_tick_mark
+-T lxw_chart_axis_tick_position
+-T lxw_chart_blank
+-T lxw_chart_error_bar_cap
+-T lxw_chart_error_bar_direction
+-T lxw_chart_error_bar_type
+-T lxw_chart_fill
+-T lxw_chart_font
+-T lxw_chart_gridline
+-T lxw_chart_label_position
+-T lxw_chart_label_separator
+-T lxw_chart_legend
+-T lxw_chart_legend_position
+-T lxw_chart_line
+-T lxw_chart_line_dash_type
+-T lxw_chart_marker
+-T lxw_chart_marker_type
+-T lxw_chart_pattern
+-T lxw_chart_pattern_type
+-T lxw_chart_point
+-T lxw_chart_series
+-T lxw_chart_title
+-T lxw_chart_trendline_type
+-T lxw_chart_type
+-T lxw_col_options
+-T lxw_col_t
+-T lxw_color_t
+-T lxw_content_types
+-T lxw_core
+-T lxw_custom
+-T lxw_custom_property
+-T lxw_datetime
+-T lxw_defined_name
+-T lxw_doc_properties
+-T lxw_drawing
+-T lxw_drawing_coords
+-T lxw_drawing_object
+-T lxw_error
+-T lxw_fill
+-T lxw_font
+-T lxw_format
+-T lxw_hash_element
+-T lxw_hash_table
+-T lxw_header_footer_options
+-T lxw_heading_pair
+-T lxw_image_options
+-T lxw_merged_range
+-T lxw_packager
+-T lxw_panes
+-T lxw_part_name
+-T lxw_print_area
+-T lxw_protection
+-T lxw_rel_tuple
+-T lxw_relationships
+-T lxw_repeat_cols
+-T lxw_repeat_rows
+-T lxw_row
+-T lxw_row_col_options
+-T lxw_row_t
+-T lxw_selection
+-T lxw_series_data_point
+-T lxw_series_error_bars
+-T lxw_series_range
+-T lxw_sst
+-T lxw_styles
+-T lxw_theme
+-T lxw_tuple
+-T lxw_workbook
+-T lxw_workbook_options
+-T lxw_worksheet
+-T lxw_worksheet_init_data
+-T lxw_worksheet_name

data/libxlsxwriter/.travis.yml

@@ -0,0 +1,25 @@
+language: c
+
+compiler:
+  - clang
+  - gcc
+
+env:
+  -                                      CFLAGS='-Werror'
+  - NO_VALGRIND=1 USE_STANDARD_TMPFILE=1 CFLAGS='-Werror'
+  - NO_VALGRIND=1                        CFLAGS='-Werror -m32'
+
+install:
+  - sudo pip install pytest
+  - sudo apt-get update
+  - sudo apt-get install -y gcc-multilib
+  - sudo apt-get install -y zlib1g-dev
+  - sudo apt-get install -y zlib1g-dev:i386
+  - sudo apt-get install -y gcc
+  - sudo apt-get install -y valgrind
+
+script:
+  - make V=1
+  - make test_functional V=1
+  - make test_unit V=1
+  - make test_valgrind V=1

data/libxlsxwriter/CONTRIBUTING.md

@@ -0,0 +1,226 @@
+# libxlsxwriter: Reporting Bugs and submitting Pull Requests
+
+
+## Reporting Bugs
+
+Here are some tips on reporting bugs in `libxlsxwriter`.
+
+### Upgrade to the latest version of the library
+
+Upgrade to the latest version of the library since the bug you are reporting
+may already be fixed.
+
+Check the [Changes][changes] section of the documentation to see what has
+changed in the latest versions.
+
+[changes]: http://libxlsxwriter.github.io/changes.html
+
+You can check which version of `libxlsxwriter` that you are using by checking
+the `xlsxwriter.h` header file or by adding the following to your program:
+
+```C
+#include <stdio.h>
+#include "xlsxwriter.h"
+
+int main() {
+
+    printf("Libxlsxwriter version = %s\n", LXW_VERSION);
+
+    return 0;
+}
+```
+
+
+### Read the documentation
+
+Read or search the `libxlsxwriter` [documentation][docs] to see if the issue
+you are encountering is already explained.
+
+[docs]: http://libxlsxwriter.github.io/index.html
+
+### Look at the example programs
+
+There are many [examples programs][examples] in the distribution. Try to
+identify an example program that corresponds to your query and adapt it to use
+as a bug report.
+
+[examples]: http://libxlsxwriter.github.io/examples.html
+
+
+### Use the xlsxwriter Issue Tracker
+
+The [libxlsxwriter issue tracker][issues] is on GitHub.
+
+[issues]: https://github.com/jmcnamara/libxlsxwriter/issues
+
+
+### Tips for submitting a bug report
+
+1.  Describe the problem as clearly and as concisely as possible.
+2.  Include a sample program. This is probably the most important step.
+    It is generally easier to describe a problem in code than in written
+    prose.
+3.  The sample program should be as small as possible to demonstrate the
+    problem. Don't copy and paste large non-relevant sections of your
+    program.
+
+A sample bug report is shown below. This format helps analyze and respond to
+the bug report more quickly.
+
+
+> Subject: Issue with SOMETHING
+>
+> Greetings,
+>
+> I am using libxlsxwriter to do SOMETHING but it appears to do SOMETHING ELSE.
+>
+> I am using CC version X.Y.Z, OS = uname and libxlsxwriter x.y.z.
+>
+> Here is some code that demonstrates the problem:
+>
+>
+>```C
+>#include "xlsxwriter.h"
+>
+>int main() {
+>
+>    lxw_workbook  *workbook  = workbook_new("bug_report.xlsx");
+>    lxw_worksheet *worksheet = workbook_add_worksheet(workbook, NULL);
+>
+>    worksheet_write_string(worksheet, 0, 0, "Hello", NULL);
+>    worksheet_write_number(worksheet, 1, 0, 123, NULL);
+>
+>    return workbook_close(workbook);
+>}
+>```
+>
+
+
+# Pull Requests and Contributing to Libxlsxwriter
+
+All patches and pull requests are welcome but in general you should start with
+an issue tracker to describe what you intend to do before you do it.
+
+
+### Getting Started
+
+1. Pull requests and new feature proposals must start with an [issue
+   tracker][issues]. This serves as the focal point for the design discussion.
+2. Describe what you plan to do. If there are API changes add some code
+   example to demonstrate them.
+3. Fork the repository.
+4. Run all the tests to make sure the current code works on your system using
+   `make test`.  See the [Running the Test Suite][tests] section of the docs
+   for instructions.
+5. Create a feature branch for your new feature.
+
+
+[tests]: http://libxlsxwriter.github.io/running_the_tests.html
+
+### Code Style
+
+The code style is mainly K&R style with 4 space indents.
+
+The author uses GNU indent (`gindent`) 2.2.10 with the following options:
+
+```
+    --braces-on-if-line
+    --braces-on-struct-decl-line
+    --case-indentation 4
+    --continue-at-parentheses
+    --declaration-comment-column 0
+    --format-first-column-comments
+    --honour-newlines
+    --ignore-profile
+    --indent-label 0
+    --indent-level 4
+    --no-space-after-function-call-names
+    --no-tabs
+    --swallow-optional-blank-lines
+```
+
+The [indent configuration file][indentpro] is available in the repo. The code
+can be indented automatically if the same version of `gindent` is used with
+the following make command:
+
+```shell
+    make indent
+```
+
+Note, make sure you have backed up your files or added them to the index
+before running this command.
+
+In general follow the existing style in the code.
+
+[indentpro]: https://github.com/jmcnamara/libxlsxwriter/blob/master/.indent.pro
+
+### Writing and Running Tests
+
+Any significant features should be accompanied by a test. See the `test`
+directory and the [Running the Test Suite][tests] section of the docs for
+details of the test setup.
+
+The tests can be run as follows:
+
+```shell
+    make test
+```
+Same as:
+
+```shell
+    make test_unit
+    make test_functional
+```
+
+The functional tests require the Python module [pytest][pytest] as a test runner.
+
+If you have `valgrind` installed you can use the test suite to check for memory leaks:
+
+```shell
+    make test_valgrind
+```
+
+When you push your changes they will also be tested automatically using
+[Travis CI][travis].
+
+[Travis]: https://travis-ci.org/jmcnamara/libxlsxwriter/
+[pytest]: http://pytest.org/
+
+
+### Documentation
+
+The `libxlsxwriter` documentation is written in Doxygen format in the header
+files and in additional `.dox` files in the `docs/src` directory of the
+repo. The documentation can be built as follows:
+
+```shell
+    make docs
+    open docs/html/index.html
+```
+
+
+### Example programs
+
+If applicable add an example program to the `examples` directory. Example
+files can be built using:
+
+```shell
+   make docs
+```
+
+### Copyright and License
+
+Copyright remains with the original author. Do not include additional
+copyright claims or Licensing requirements. GitHub and the `git` repository
+will record your contribution and it will be acknowledged it in the Changes
+file.
+
+
+### Submitting the Pull Request
+
+If your change involves several incremental `git` commits then `rebase` or
+`squash` them onto another branch so that the Pull Request is a single commit
+or a small number of logical commits.
+
+Push your changes to GitHub and submit the Pull Request with a hash link to
+the to the Issue tracker that was opened above.