Regarding the build process (mainly for SciTE, but also for Scintilla and Lexilla)

------=_Part_23150_2105401410.1746513191632
Content-Type: multipart/alternative; 
	boundary="----=_Part_23151_1157036620.1746513191632"

------=_Part_23151_1157036620.1746513191632
Content-Type: text/plain; charset="UTF-8"

Hi there,

I've been maintaining the FreeBSD port of SciTE (and by extension, 
Scintilla and later Lexilla) for many years now, but I've always been a bit 
baffled by the build process for them. From my understanding, it appears as 
if they aren't really designed to be built and installed separately from 
each other, that all of them are expected to be built together. I've tried 
working around that with the FreeBSD ports, so that there can be 3 separate 
ones (there is x11-toolkits/scintilla for Scintilla, textproc/lexilla for 
Lexilla and editors/scite for Scite). However, I've found that with the way 
the build process currently is, SciTE does not appear to actually link to 
any Lexilla shared library, but it does link with Scintilla's shared 
library. And I've also found that Lexilla only seems to need Scintilla for 
building and rely on Scintilla's library in any way.

So mainly, I'd like some insight about how to properly build all 3 in such 
a way that they can be treated as separate, individual entities and that 
they can be installed individually and used in the build process outside of 
what is included in the tarball (as I've noticed that SciTE's tarball 
contains both the source code of Lexilla and Scintilla in it).

Thanks in advance,
Naram "CyberBotX" Qashat

-- 
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/scite-interest/1c9257b7-c288-4fb7-9768-e6b427404191n%40googlegroups.com.

------=_Part_23151_1157036620.1746513191632
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div>Hi there,</div><div><br /></div><div>I've been maintaining the FreeBSD=
 port of SciTE (and by extension, Scintilla and later Lexilla) for many yea=
rs now, but I've always been a bit baffled by the build process for them. F=
rom my understanding, it appears as if they aren't really designed to be bu=
ilt and installed separately from each other, that all of them are expected=
 to be built together. I've tried working around that with the FreeBSD port=
s, so that there can be 3 separate ones (there is x11-toolkits/scintilla fo=
r Scintilla, textproc/lexilla for Lexilla and editors/scite for Scite). How=
ever, I've found that with the way the build process currently is, SciTE do=
es not appear to actually link to any Lexilla shared library, but it does l=
ink with Scintilla's shared library. And I've also found that Lexilla only =
seems to need Scintilla for building and rely on Scintilla's library in any=
 way.</div><div><br /></div><div>So mainly, I'd like some insight about how=
 to properly build all 3 in such a way that they can be treated as separate=
, individual entities and that they can be installed individually and used =
in the build process outside of what is included in the tarball (as I've no=
ticed that SciTE's tarball contains both the source code of Lexilla and Sci=
ntilla in it).</div><div><br /></div><div>Thanks in advance,</div><div>Nara=
m "CyberBotX" Qashat</div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;scite-interest&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:[email protected]">scit=
[email protected]</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
scite-interest/1c9257b7-c288-4fb7-9768-e6b427404191n%40googlegroups.com?utm=
_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/scit=
e-interest/1c9257b7-c288-4fb7-9768-e6b427404191n%40googlegroups.com</a>.<br=
 />

------=_Part_23151_1157036620.1746513191632--

------=_Part_23150_2105401410.1746513191632--