https://wiki.raptorcs.com/w/index.php?title=Porting/Briar&feed=atom&action=historyPorting/Briar - Revision history2024-03-28T17:36:43ZRevision history for this page on the wikiMediaWiki 1.33.1https://wiki.raptorcs.com/w/index.php?title=Porting/Briar&diff=3463&oldid=prevJeremyRand: Add BE notes2021-04-29T05:29:53Z<p>Add BE notes</p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 05:29, 29 April 2021</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>It is possible to build Briar from source for <del class="diffchange diffchange-inline">POWER </del>(tested on Debian Bullseye <del class="diffchange diffchange-inline">for ppc64le</del>). To do this, follow the [https://code.briarproject.org/briar/briar-gtk#directly-from-source Directly from source] instructions for Briar-GTK. When building Briar Headless, you'll need to follow the additional instructions from the "To get Briar running on ARM devices" section of [https://nico.dorfbrunnen.eu/posts/2021/briar-remote/ Using Briar GTK at a distance]. The patch no longer applies cleanly, but it's trivial and obvious how to resolve the conflict.</div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">== ppc64le ==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>It is possible to build Briar from source for <ins class="diffchange diffchange-inline">ppc64le </ins>(tested on Debian Bullseye). To do this, follow the [https://code.briarproject.org/briar/briar-gtk#directly-from-source Directly from source] instructions for Briar-GTK. When building Briar Headless, you'll need to follow the additional instructions from the "To get Briar running on ARM devices" section of [https://nico.dorfbrunnen.eu/posts/2021/briar-remote/ Using Briar GTK at a distance]. The patch no longer applies cleanly, but it's trivial and obvious how to resolve the conflict<ins class="diffchange diffchange-inline">.</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">== ppc64be ==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">Briar Headless fails to run on ppc64be when built using the ppc64le instructions, because <code>libjnidispatch.so</code> for ppc64be is not included in the binaries pulled in by Gradle. This could be fixed if [https://code.briarproject.org/briar/python-briar-wrapper/-/issues/15 Add option to use system's Tor binary] were implemented</ins>.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:Ports]]</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:Ports]]</div></td></tr>
<!-- diff cache key raptorcs_wikidb-mediawiki-:diff::1.12:old-3462:rev-3463 -->
</table>JeremyRandhttps://wiki.raptorcs.com/w/index.php?title=Porting/Briar&diff=3462&oldid=prevJeremyRand: Add Briar porting page2021-04-28T22:39:46Z<p>Add Briar porting page</p>
<p><b>New page</b></p><div>It is possible to build Briar from source for POWER (tested on Debian Bullseye for ppc64le). To do this, follow the [https://code.briarproject.org/briar/briar-gtk#directly-from-source Directly from source] instructions for Briar-GTK. When building Briar Headless, you'll need to follow the additional instructions from the "To get Briar running on ARM devices" section of [https://nico.dorfbrunnen.eu/posts/2021/briar-remote/ Using Briar GTK at a distance]. The patch no longer applies cleanly, but it's trivial and obvious how to resolve the conflict.<br />
<br />
[[Category:Ports]]</div>JeremyRand