search

tazdij / raylib-pas

A complete header translation (binding) of the raylib 2.6.0-dev to Pascal. Without any funky helper functions for memory alignment issues. Inspired and partially based on the drezgames/raylib-pascal binding, however a little cleaner and more recent, with FPC 3.0.4 support.
28 stars 5 forks source link

Prebuilt Binary of Raylib #5

Open tazdij opened 4 years ago

tazdij commented 4 years ago

I want to include a Prebuilt Binary of Raylib at the exact Commit which raylib-pas targets. This could alleviate issues with users downloading a newer "Master" than we are currently targeting and running into breaking API or Memory Layout changes in raylib. Plus this should make it simpler for Delphi/FreePascal Developers who may not have a lot of experience compiling C libraries or using CMake.

I will do my best to include the latest targeted binaries, however, I do not readily have a MacOS computer which I can use to build the raylib .dylib and .a files on. I can provide the Linux and Windows binaries.

Anyone want to help with the MacOS ones?

ludoza commented 4 years ago 
$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.14.6
BuildVersion:   18G1012

We must just also face the depreciation warnings.

Morabaraba commented 4 years ago 
$ hostnamectl
   ...
  Operating System: Ubuntu 19.04
            Kernel: Linux 5.0.0-32-generic
      Architecture: x86-64
ludoza commented 4 years ago

Hi @tazdij

As shown above I added raylib to a ci pipeline on gitlab and zip the needed libraylib.* files for ubuntu and macos. We can maybe now add these links to the README.md for users that want the latest raylib binaries:

Might also be worth while to ask @raysan5 if he will accept a merge request for .gitlab-ci.yaml then the mirror and runner will just build the ci packages as raylib commit changes.

Later,

zaher commented 4 years ago

I think it is wrong idea, you job should be just header for last stable version of raylib released offically providing rebuild binary, will duplicate work of raylib did, and it will be non trusted. I always when doing header and framework, use the version provided from main site, like sqlite, FirebirdSQL, PostgreSQL etc.

tazdij commented 4 years ago

The old version of raylib lacks many features and has some bugs. We are targeting the master branch, and this will require the pascal developer to download the raylib source and compile it. This is a step and toolchain most pascal developers are not familiar with.

On Nov 24, 2019 07:42, Zaher Dirkey notifications@github.com wrote:I think it is wrong idea, you job should be just header for last stable version of raylib released offically providing rebuild binary, will duplicate work of raylib did, and it will be non trusted. I always when doing header and framework, use the version provided from main site, like sqlite, FirebirdSQL, PostgreSQL etc.

—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.