xlsxio library

[fxl447098457]

added xlsxio library and read/write demos

[jayrm]

Thank-you for the pull request. Which version of fbfrog was used?

Would it be possible to provide the URLs of the downloaded sources?

The work flow currently for this repo is to modify the makefile to automatically download and unpack sources, then automatically translate bindings with fbfrog+scripts on the raw branch, manually merge to master branch, then make all the hand edits. The idea being to automate as much as possible so that when upstream headers are updated they can be run through the same process preserving the difference of hand edits from one version of the library to the next.

[fxl447098457]

Thank-you for the pull request. Which version of fbfrog was used?
fbfrog 1.14

Would it be possible to provide the URLs of the downloaded sources?
all the sources could be downloaded form github.most libraries come from awesome c list(https://github.com/oz123/awesome-c)

[jayrm]

fbfrog 1.14

Sorry, I meant revision / commit. do you know the hash of the commit?
Like, was it exactly fbfrog 'v1.14' tag? or was it some later revision?

The fbbindings build script will grab a specific fbfrog repository commit to work with

[fxl447098457]

the cmd display:fbfrog 1.14 compiled on 2023-12-01.so it should be the lasted version.If there's anything I can do to reduce your workload, feel free to let me know.

[jayrm]

hey @fxl447098457

the cmd display:fbfrog 1.14 compiled on 2023-12-01.so it should be the lasted version.If there's anything I can do to reduce your workload, feel free to let me know.

Ideally we would like to have automation for regenerating the translated headers. If fbfrog improves it is good to be able to rerun the translations. And if there is manual edits, then some way to capture that. Or if the library version is upgraded, be able to rerun the translations on the new version, and reintegrate the manual edits (assuming the headers didn't change too much).

The fbbindings repo has this workflow:

1. automated translations on raw branch
2. merge raw to master
3. manual edits and tests on master branch

For example, I looked at your commits for zstd. I am guessing you are running and testing windows only?

1. add zstd rule to the main makefile and run make or make zstd to generate first version of the machine translated headers files as in commit [13f4cf7]

2. checkout master and merge in raw as seen in commit [28a9065]

3. make manual edits
   a) cherry picked your commit to add the tests [88f9a40]
   b) manually edit the license information because I didn't find an easy way to automate this. (besides, your commit refers to BFD library and seems incorrect so would need to be edit again anyway) [af9f9cf]
   c) normalize line endings - not a problem exactly, but will show up eventually when diff-ing files, so everything checked should have LF line endings - because code base will be checked out on both linux and windows [507512c]

--- so,

I run the tests and get an error - that's ok, I use this opportunity to show the continued workflow:
$ make tests

~/fb/fbbindings.git/inc/zstd/zstd.bi(56) error 4: Duplicated definition, found 'iif' in 'declare function ZSTD_compressBound(byval srcSize as uinteger) as uinteger'

$ git checkout raw
edit zstd.frog and add a -renamedefine option
$ make zstd - this will regenerate the files : [77ca384]
$ git checkout master
$ git merge raw - now notice that do not need to manually edit the header again, since changes are merged, not replaced as can be seen in [0ae999b]

--- next,

I run the tests again and now we have

TEST linux-x86 tests/zstd_simple_compression.bas
/usr/local/include/freebasic/crt/sys/stat.bi(18) error: Unsupported platform

This is a bigger problem to solve since the whole crt is not fully translated for every platform. Or need to disable this test for some platforms. Or rewrite the test using functions that are easier to port between platforms.

I hope this kind of helps to show what kind of testing and quality checks go in to the project.

I stop now for the day.