Well, I guess I could do that, but the version number of the most
recent version of QScintilla2 would have to be statically set and
updated in a separate build script (currently it's just a matter of 1.
svn co .... 2. qmake 3. make). If I had an external repo set up, I
could maintain my current build steps without having to write and
maintain a separate build script.
So, I wouldn't say that I _need_ an external repo, but it would be
nice. Does that make sense?
Thanks,
Jared
On 10/23/2010 06:05 AM, Hans-Peter Jansen wrote:
On Saturday 23 October 2010, 03:32:15 Jared Sutton wrote:
Is there a public SVN server available for QScintilla2? It would
really help the build process for my project if I could setup an
external repo to automatically build qscintilla (especially on Mac OS
X, where building a static libqscintilla2.a is preferable).
Do you say, that you need a public SVN server to build a statically
linked package? Can't your build process handle released tarballs?
Puzzled,
Pete
_______________________________________________
QScintilla mailing list
[email protected]
http://www.riverbankcomputing.com/mailman/listinfo/qscintilla
_______________________________________________
QScintilla mailing list
[email protected]
http://www.riverbankcomputing.com/mailman/listinfo/qscintilla
