Re: New home for B2.
Tarmo Pikaro via Boost-build <[email protected]> Mon, 8 Mar 2021 16:38:49 +0000 (UTC)
| Newsgroups | gmane.comp.lib.boost.build,gmane.comp.lib.boost.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============0175993928188064367==
Content-Type: multipart/alternative;
boundary="----=_Part_530304_135434369.1615221529042"
------=_Part_530304_135434369.1615221529042
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi !
B2 homepage looks rather pretty indeed.
Have anyone ever considered to create SDK style project for C++ support ?
I by myself was using both - C++ and C# in my own projects, and I found C# =
/ SDK style project as much easier to use than cmake.Of course B2 is slight=
ly different than cmake, but I think at the end it will also generate some =
sort of build files.
For Windows / Visual studio build files are nice, but it's easier just to p=
ass information from files to Visual Studio.
I have posted similar kind of comment to cmake forums:=C2=A0https://gitlab.=
kitware.com/cmake/cmake/-/issues/20227#note_898893
And I see two ways help C++ to evolve - one is visual studio specific using=
c# / props files / project in C++/SDK style,another is to help C++ to beco=
me scriptable.
I think first approach might be more realistic than second one.
-- Have a nice day!=C2=A0 =C2=A0 =C2=A0Tarmo.=20
On Monday, March 8, 2021, 05:34:52 PM GMT+2, Ren=C3=A9 Ferdinand Rivera=
Morell via Boost-build <[email protected]> wrote: =20
=20
As some of you may have noticed, B2 has a new home outside the Boost organ=
ization at <https://www.bfgroup.xyz/b2/>. The goal of the move is to elevat=
e B2 development above the constraints of the Boost structure. I.e. to make=
B2 not just the build system that Boost uses.
The biggest change to make happen is that last week the B2 fork at <https:/=
/github.com/bfgroup/b2> became the base git repo of all existing B2 git rep=
os. And hence it means that the git repo <https://github.com/boostorg/build=
> is now a fork. What does this mean going forward?
This that will not change:
* Boost will still get the build system from the same git repo as it does n=
ow.* The B2 documentation will still be included in the Boost releases.
What will change (eventually), or has already changed:
* Development has moved to the new B2 git repo. And hence PRs for B2 will n=
eed to be posted to the new repo.* The B2 mail list at <https://lists.boost=
.org/mailman/listinfo.cgi/boost-build> will be replaced by the GitHub discu=
ssion forums at <https://github.com/bfgroup/b2/discussions>.* The B2 versio=
n in Boost will be updated from the base git repo for releases of the B2 ba=
se only. I.e. a B2 release will get merged to the Boost develop branch. And=
from there to the master branch.* The Boost testing of B2 reported at <htt=
ps://www.boost.org/development/tests/develop/developer/summary.html> will s=
top showing (and hence running) B2 tests.The testing has already moved to c=
loud CI. And expanded to cover more platforms than Boost usually tests.* Th=
e B2 web site at <https://boostorg.github.io/build/> will go away.
* The issues at <https://github.com/boostorg/build/issues> will eventually =
go away (once I deal with enough of them).
--=20
-- Ren=C3=A9 Ferdinand Rivera Morell
-- Don't Assume Anything=C2=A0 -- No Supone Nada
-- Robot Dreams -=C2=A0http://robot-dreams.net
_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/b=
oost-build
=20
------=_Part_530304_135434369.1615221529042
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<html><head></head><body><div class=3D"ydp79ad0095yahoo-style-wrap" style=
=3D"font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 1=
3px;"><div><div dir=3D"ltr" data-setdir=3D"false">Hi !</div><div dir=3D"ltr=
" data-setdir=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"false">B2=
homepage looks rather pretty indeed.</div><div dir=3D"ltr" data-setdir=3D"=
false"><br></div><div dir=3D"ltr" data-setdir=3D"false">Have anyone ever co=
nsidered to create SDK style project for C++ support ?</div><div dir=3D"ltr=
" data-setdir=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"false">I =
by myself was using both - C++ and C# in my own projects, and I found C# / =
SDK style project as much easier to use than cmake.</div><div dir=3D"ltr" d=
ata-setdir=3D"false">Of course B2 is slightly different than cmake, but I t=
hink at the end it will also generate some sort of build files.</div><div d=
ir=3D"ltr" data-setdir=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"=
false">For Windows / Visual studio build files are nice, but it's easier ju=
st to pass information from files to Visual Studio.</div><div dir=3D"ltr" d=
ata-setdir=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"false">I hav=
e posted similar kind of comment to cmake forums: <a href=3D"https://g=
itlab.kitware.com/cmake/cmake/-/issues/20227#note_898893" rel=3D"nofollow" =
target=3D"_blank">https://gitlab.kitware.com/cmake/cmake/-/issues/20227#not=
e_898893</a></div><div dir=3D"ltr" data-setdir=3D"false"><br></div><div dir=
=3D"ltr" data-setdir=3D"false">And I see two ways help C++ to evolve - one =
is visual studio specific using c# / props files / project in C++/SDK style=
,</div><div dir=3D"ltr" data-setdir=3D"false">another is to help C++ to bec=
ome scriptable.</div><div dir=3D"ltr" data-setdir=3D"false"><br></div><div =
dir=3D"ltr" data-setdir=3D"false">I think first approach might be more real=
istic than second one.</div><div dir=3D"ltr" data-setdir=3D"false"><br></di=
v><div dir=3D"ltr" data-setdir=3D"false"><br></div><div class=3D"ydp79ad009=
5signature">-- Have a nice day!<div> Tarmo.</div></di=
v></div>
<div><br></div><div><br></div>
=20
</div><div id=3D"ydp3c80b53cyahoo_quoted_6078312513" class=3D"ydp3c=
80b53cyahoo_quoted">
<div style=3D"font-family:'Helvetica Neue', Helvetica, Arial, s=
ans-serif;font-size:13px;color:#26282a;">
=20
<div>
On Monday, March 8, 2021, 05:34:52 PM GMT+2, Ren=C3=A9 =
Ferdinand Rivera Morell via Boost-build <[email protected]>=
wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id=3D"ydp3c80b53cyiv5134760446"><div dir=3D"ltr">=
<div>As some of you may have noticed, B2 has a new home outside the Boost o=
rganization at <<a href=3D"https://www.bfgroup.xyz/b2/" rel=3D"nofollow"=
target=3D"_blank">https://www.bfgroup.xyz/b2/</a>>. The goal of the mov=
e is to elevate B2 development above the constraints of the Boost structure=
. I.e. to make B2 not just the build system that Boost uses.<br></div><div>=
<br></div><div>The biggest change to make happen is that last week the B2 f=
ork at <<a href=3D"https://github.com/bfgroup/b2" rel=3D"nofollow" targe=
t=3D"_blank">https://github.com/bfgroup/b2</a>> became the base git repo=
of all existing B2 git repos. And hence it means that the git repo <<a =
href=3D"https://github.com/boostorg/build" rel=3D"nofollow" target=3D"_blan=
k">https://github.com/boostorg/build</a>> is now a fork. What does this =
mean going forward?</div><div><br></div><div>This that will not change:</di=
v><div><br></div><div>* Boost will still get the build system from the same=
git repo as it does now.</div><div>* The B2 documentation will still be in=
cluded in the Boost releases.</div><div><br></div><div>What will change (ev=
entually), or has already changed:</div><div><br></div><div>* Development h=
as moved to the new B2 git repo. And hence PRs for B2 will need to be poste=
d to the new repo.</div><div>* The B2 mail list at <<a href=3D"https://l=
ists.boost.org/mailman/listinfo.cgi/boost-build" rel=3D"nofollow" target=3D=
"_blank">https://lists.boost.org/mailman/listinfo.cgi/boost-build</a>> w=
ill be replaced by the GitHub discussion forums at <<a href=3D"https://g=
ithub.com/bfgroup/b2/discussions" rel=3D"nofollow" target=3D"_blank">https:=
//github.com/bfgroup/b2/discussions</a>>.</div><div>* The B2 version in =
Boost will be updated from the base git repo for releases of the B2 base on=
ly. I.e. a B2 release will get merged to the Boost develop branch. And from=
there to the master branch.</div><div>* The Boost testing of B2 reported a=
t <<a href=3D"https://www.boost.org/development/tests/develop/developer/=
summary.html" rel=3D"nofollow" target=3D"_blank">https://www.boost.org/deve=
lopment/tests/develop/developer/summary.html</a>> will stop showing (and=
hence running) B2 tests.The testing has already moved to cloud CI. And exp=
anded to cover more platforms than Boost usually tests.</div><div>* The B2 =
web site at <<a href=3D"https://boostorg.github.io/build/" rel=3D"nofoll=
ow" target=3D"_blank">https://boostorg.github.io/build/</a>> will go awa=
y.<br></div><div>* The issues at <<a href=3D"https://github.com/boostorg=
/build/issues" rel=3D"nofollow" target=3D"_blank">https://github.com/boosto=
rg/build/issues</a>> will eventually go away (once I deal with enough of=
them).</div><div><br>-- <br><div dir=3D"ltr" class=3D"ydp3c80b53cyiv513476=
0446gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr">-- Ren=C3=A9 Fe=
rdinand Rivera Morell<br>-- Don't Assume Anything -- No Supone Nada<b=
r>-- Robot Dreams - <a href=3D"http://robot-dreams.net/" rel=3D"nofoll=
ow" target=3D"_blank">http://robot-dreams.net</a><br><br></div></div></div>=
</div></div></div>
</div>_______________________________________________<br>Unsubscribe & =
other changes: <a href=3D"https://lists.boost.org/mailman/listinfo.cgi/boos=
t-build" rel=3D"nofollow" target=3D"_blank">https://lists.boost.org/mailman=
/listinfo.cgi/boost-build</a><br></div>
</div>
</div></body></html>
------=_Part_530304_135434369.1615221529042--
--===============0175993928188064367==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
--===============0175993928188064367==--