How to setup Clarion development environment in Git (BitBucket or GitHub)

ide Tips
1

Create repository in Bitbucket/GitHub

image
image773×728 75.7 KB

Go to Repository Settings → GIT LFS (or Repository Details). Enable LFS is it is not already enabled.

Copy the Clone URL.

On your workstation:

Using Git tools or Git command line make sure LFS is installed for the repository.

For SmartGit:

Assuming your Clarion Folder is C:\Clarion11

Rename C:\Clarion11 to C:\Clarion11_Good

Clone the repository (repo) created in the first step to C:\Clarion11.

From the Local menu option. Pick LFS → Install. Say “Yes” to any confirmation prompts.

image
image825×809 108 KB

Using File Explorer or command line copy the all files and folders from C:\Clarion11_Good to C:\Clarion11

Create/Copy .gitignore and .gitattributes files in the root of C:\Clarion11.

Here are examples:

.gitignore

/BACKUP

*.XLOG

/D32.LOG

/CLARIO~1.chw

/ClarionHelp.chw

/ClarionNet20.red

Thumbs.db

.gitattributes

*.{dll,Dll,DLL,dct,DCT,exe,Exe,EXE,lib,LIB,obj,ocx,ovl,pack,bin,pak,svg,swf,tps,Tps,TPS,trf} filter=lfs diff=lfs merge=lfs -text

*.dll filter=lfs diff=lfs merge=lfs -text

*.dct filter=lfs diff=lfs merge=lfs -text

*.exe filter=lfs diff=lfs merge=lfs -text

*.lib filter=lfs diff=lfs merge=lfs -text

*.obj filter=lfs diff=lfs merge=lfs -text

*.ocx filter=lfs diff=lfs merge=lfs -text

*.ovl filter=lfs diff=lfs merge=lfs -text

*.pack filter=lfs diff=lfs merge=lfs -text

*.bin filter=lfs diff=lfs merge=lfs -text

*.pak filter=lfs diff=lfs merge=lfs -text

*.svg filter=lfs diff=lfs merge=lfs -text

*.swf filter=lfs diff=lfs merge=lfs -text

*.tps filter=lfs diff=lfs merge=lfs -text

*.trf filter=lfs diff=lfs merge=lfs -text

In SmartGit select the Clarion11 folder and Stage all files.

Commit and Push all files as “Clarion11 initial revision”

Additional considerations:

If you modify shipping source files or template files, and even if you don’t, I strongly recommend you create a branch now called SoftVelocity. Don’t check it out, just created. Use this branch for applying new Clarion updates as a vendor branch.

I would also create a vendor branch called CapeSoftProducts, if you use CapeSoft and might make modifications to their source files.

2 Likes