GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - livecode/livecode-thirdparty

This repository was archived by the owner on Aug 31, 2021. It is now read-only.
BranchesTags
Open more actions menu

Latest commit

 

History

631 Commits
631 Commits

Folders and files

NameName
Last commit message
Last commit date
headers/linux/include
headers/linux/include
 
 
libcairo
libcairo
 
 
libcef
libcef
 
 
libcurl
libcurl
 
 
libexpat
libexpat
 
 
libffi
libffi
 
 
libfreetype
libfreetype
 
 
libgif
libgif
 
 
libharfbuzz
libharfbuzz
 
 
libiodbc
libiodbc
 
 
libjpeg
libjpeg
 
 
libmysql
libmysql
 
 
libopenssl
libopenssl
 
 
libpcre
libpcre
 
 
libpng
libpng
 
 
libpq
libpq
 
 
libskia
libskia
 
 
libsqlite
libsqlite
 
 
libxml
libxml
 
 
libxslt
libxslt
 
 
libz
libz
 
 
libzip
libzip
 
 
tools
tools
 
 
.gitattributes
.gitattributes
 
 
.gitignore
.gitignore
 
 
README.md
README.md
 
 
owner
owner
 
 

Repository files navigation

LiveCode Thirdparty Libraries

The procedure for updating thirdparty on develop-9.0 and develop branches is slightly different due to thirdparty prebuilts on develop.

Update procedure for develop-9.0

  1. Push up a PR to this repo
  2. If there is a related patch to another repos then push up a PR for those
  3. Create a test branch on livecode with updated submodule ptrs. Ensure the branch is pushed upstream rather than to your clone.
  4. If it was a CEF update then push up a branch to livecode-private again with updated submodule and kick off prebuilts on vulcan.
  5. Create a PR with the title beginning with [[ NO MERGE ]] and review it ok to confirm it passes on travis and vulcan
  6. Close PR from 5 and link to it in the other related PRs
  7. Once all related PRs are reviewed merge thirdparty, update submodules in livecode and merge any related PRs

Update procedure for develop

The same procedure applies to merge-ups from develop-9.0 because the thirdparty prebuilts must be rebuilt for the current head of the develop branch.

  1. Push up a PR to this repo
  2. If there is a related patch to another repos then push up a PR for those
  3. Review and merge the PR for thirdparty but do not update submodule ptrs in livecode yet.
  4. Create a test branch on livecode with updated submodule ptrs. Ensure the branch is pushed upstream rather than to your clone.
  5. Push up a branch to livecode-private again with updated submodule and kick off prebuilts on vulcan.
  6. Once prebuilts are built for the develop head of thirdparty create a PR using the livecode branch with the title beginning with [[ NO MERGE ]] and review it ok to confirm it passes on travis and vulcan
  7. Close PR from 6 and link to it in the other related PRs
  8. Once all related PRs are reviewed, update submodules in livecode and merge any related PRs

About

No description, website, or topics provided.

Resources

Readme
Activity
Custom properties

Stars

11 stars

Watchers

8 watching

Forks

31 forks
Report repository

Releases

Packages

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.