Closed GoogleCodeExporter closed 8 years ago
* CC'ing David Dorothy on this, since he made the change and does development
on OS X.
The issue is that both David and I failed to get QScintilla2 to build as a
framework on OS X. Building as a static lib was the easiest way to get this
working correctly. Also, when we distribute an OS X binary, it simplifies
installation, since the user doesn't need to copy a framework in to a
Library/Frameworks folder (the static lib is copied into the .app bundle).
Does that make sense? BTW, good to see you're still alive, Ben. :)
-Jared
Original comment by jpsut...@gmail.com
on 22 Oct 2010 at 3:42
Yeah. Wish Apple would let us put dynamic libraries inside a .app.
I think y'all are right that static is harder to get wrong. In that case, do we
want to import the qscintilla sources into our tree and build it from our make?
Original comment by bfrobin...@gmail.com
on 22 Oct 2010 at 3:59
Yeah, that sounds like the best approach right now. Doesn't subversion have a
way of referencing external repositories?
Original comment by jpsut...@gmail.com
on 22 Oct 2010 at 4:02
See http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html
Ben, could you set this up?
Original comment by jpsut...@gmail.com
on 22 Oct 2010 at 4:15
I know how to do an external in Subversion, but I can't find an svn repository
for qscintilla. Anyone know of one?
Original comment by bfrobin...@gmail.com
on 22 Oct 2010 at 7:34
I'm on the dev list. I'll ask later when I can type a proper email... :)
Original comment by jpsut...@gmail.com
on 22 Oct 2010 at 7:44
I sent this question out on the list, and the response was basically "use the
tarball releases." I guess we'll just need to pull a copy of QScintilla2 into
our source tree and update it periodically until a better solution becomes
available. After that, we should be able to automate the build process of the
static lib.
The QTermWidget branch should have an example of building a dependent static
lib on-the-fly.
-Jared
Original comment by jpsut...@gmail.com
on 1 Nov 2010 at 11:56
OK, I've added a new build script as of r204 to automatically download the
latest stable QScintilla2 and build a static lib. It's really basic now, but
it should suffice for now.
Ben, can you test it on a fresh checkout on OS X?
Original comment by jpsut...@gmail.com
on 3 Nov 2010 at 1:42
Oh, I should mention a few other details of the current script...
1. It does the entire qscite build
2. It builds a release, not debug build
3. This is meant as a starting point, not the end-all of build scripts. :)
Original comment by jpsut...@gmail.com
on 3 Nov 2010 at 1:53
The build script has been improved immensely since my initial commit. It
essentially performs the same tasks, but it has some error handling and a
"clean" option to do a fresh build (downloads and builds a fresh copy of
libqscintilla2.a, and does a clean build of QSciTE).
Anyone want to test and/or patch this on OS X for me? Anyone? Bueller? Fry?
Fry?
Original comment by jpsut...@gmail.com
on 4 Nov 2010 at 12:26
I refactored so you qmake qscite-whatever.pro and the Makefile handles
downloading and building QScintilla. I will continue trying to find bugs on OS
X; please report any bugs on Linux.
Original comment by bfrobin...@gmail.com
on 5 Nov 2010 at 6:44
Works for me on Linux.
Original comment by jpsut...@gmail.com
on 6 Nov 2010 at 12:49
Original issue reported on code.google.com by
bfrobin...@gmail.com
on 22 Oct 2010 at 3:37