Arch Linux User Repository

Two months have gone - no official ArchLinux or upstream pango/harfbuzz have come up... I've made a temporary hack/patch that again will enable end-users to compile this codelite AUR package without hazzle.

The pkgrel will NOT be bumped - it is a deliberate choise. My change will bring no value to those of you who have managed to build the current release of codelite - and those that have failed to build codelite during the last two months will not be notified by the pkgrel bump anyway....

Please speak up if you think this is wrong :-)

ATTENTION: read this before flagging this package out-of-date

A number of you have recently flagged package out-of-date

This package "codelite" represents the stable release of the codelite project.

I do not consider the "Weekly Builds" from http://downloads.codelite.org/ as stable releases (neither does the codelite project)

Also note: currently codelite weekly builds are only published as binary packages - this package builds from source - you should take a look at the codelite-bin AUR package)

Generally speaking - I will not update this package before the codelite github release page (https://github.com/eranif/codelite/releases) have the release published.

Please respect that - Thanks

You can always do you own "codelite-weekly" AUR package if you like...

PS: to clear up a recent misunderstanding - this does not mean that I won't accept patches that is needed for stable codelite to build against refreshed libraries etc

Two months have gone - no official ArchLinux or upstream pango/harfbuzz have come up... I've made a temporary hack/patch that again will enable end-users to compile this codelite AUR package without hazzle.

The pkgrel will NOT be bumped - it is a deliberate choise. My change will bring no value to those of you who have managed to build the current release of codelite - and those that have failed to build codelite during the last two months will not be notified by the pkgrel bump anyway....

Please speak up if you think this is wrong :-)

@ryanw that's actually works for me but with another file so thank you.

I can success build from source after edit two files /usr/include/pango-1.0/pango/pango-features.h and /usr/include/pango-1.0/pango/pango-font.h. in the files change code #include <hb.h> to #include <harfbuzz/hb.h>

Got a new computer and needed this to build, so I just made temporary symlinks in /usr/include to all the C header files in /usr/include/harfbuzz. It's dirty, but it works. You're gonna want to remove the symlinks when you're done or at least until you've built everything you need to that relies on this wonky pango.

NOTE: (2019-08-14)

Recent pango (package) releases have created a problem related to inclusion of harfbuzz/hb.h file. The problem will prevent CodeLite and other applications from compiling properly. Currently CodeLite will not compile unless the cmakefiles are hacked - but I'm still hoping for an upstream pango/harfbuzz fix...

@schnedan my comment about stable relases only relates to codelite itself - it has nothing to do with not wanting to accept a patch - which I have applied now.

Thanks to hpmachining. Works like a charm. Hint: I needed to adjust the md5sum...

Well personally I think the maintainer comment is... lets say bullshit. The community should focus on a working system. For me the computer is a productivity tool, and a IDE especially. If we can fix it we should. Waiting for upstream to appear on my computer broke my systems to often for my taste.

so again: thanks folks for getting the work done!

Maybe it's time for an orphan request.

I'm not the maintainer, so I can't update the PKGBUILD.

Ah, got it. Could you update the PKGBUILD to reflect those changes? It seems to work fine for me.