#
1e60bdea |
|
30-Mar-2019 |
Augustin Cavalier <waddlesplash@gmail.com> |
Remove all invocations of SetSubDirSupportedPlatformsBeOSCompatible.
|
#
272510c3 |
|
28-Nov-2017 |
Alexander von Gluck IV <kallisti5@unixzen.com> |
bfs_tools/bfsinfo: Cleanup output, use human sizes * Correct some warnings on 64-bit
|
#
220d0402 |
|
31-Jul-2014 |
Oliver Tappe <zooey@hirschkaefer.de> |
Use libstdc++, libsupc++ and libgcc from gcc_syslibs. * Instead of faking libstdc++.so from libstdc++.a, use libstdc++.so from the gcc_syslibs build feature for everything except x86_gcc2. * Use libgcc_s.so from the gcc_syslibs build feature for everything but x86_gcc2 (which still carries libgcc as part of libroot.so). * Drop filtering of libgcc objects for libroot, as that is no longer necessary since we're only using libgcc-as-single-object for libroot with x86_gcc2, where the filtered object file doesn't exist. Should the objects that used to be filtered cause any problems as part of libgcc_s.so, we can always filter them as part of the gcc build. * Use libsupc++.so from the gcc_syslibs build feature for everything but x86_gcc2. * Adjust all Jamfiles accordingly. * Deactivate building of faked libstdc++.so for non-x86-gcc2. For x86_gcc2, we still build libstdc++.so from the sources in the Haiku source tree as part of the Haiku build . * Put gcc_syslibs package onto the image, when needed.
|
#
be06c5a5 |
|
26-Mar-2012 |
François Revol <revol@free.fr> |
Build fix Reuse haiku-utils_rsrc jam var from upper Jamfile.
|
#
a59d56fa |
|
26-Mar-2012 |
François Revol <revol@free.fr> |
gcc4 build fixes.
|
#
647cff2e |
|
26-Mar-2012 |
Axel Dörfler <axeld@pinc-software.de> |
Imported BFS-Tools (without docs), added bfsinfo to the image. * The sources are unchanged, and most of it doesn't follow Haiku's coding style -- stuff that I updated over the years might also have seen a coding style update. * This was also the basis on which Haiku's BFS has been written. * In the long run, the stuff in 'lib' that is already part of BFS should be removed, and used directly from BFS itself. * I haven't yet added any other of the tools to the image. Not sure if they are ready for inclusion yet; 'recover' could also be renamed to reflect that it is BFS specific.
|
#
220d04022750f40f8bac8f01fa551211e28d04f2 |
|
31-Jul-2014 |
Oliver Tappe <zooey@hirschkaefer.de> |
Use libstdc++, libsupc++ and libgcc from gcc_syslibs. * Instead of faking libstdc++.so from libstdc++.a, use libstdc++.so from the gcc_syslibs build feature for everything except x86_gcc2. * Use libgcc_s.so from the gcc_syslibs build feature for everything but x86_gcc2 (which still carries libgcc as part of libroot.so). * Drop filtering of libgcc objects for libroot, as that is no longer necessary since we're only using libgcc-as-single-object for libroot with x86_gcc2, where the filtered object file doesn't exist. Should the objects that used to be filtered cause any problems as part of libgcc_s.so, we can always filter them as part of the gcc build. * Use libsupc++.so from the gcc_syslibs build feature for everything but x86_gcc2. * Adjust all Jamfiles accordingly. * Deactivate building of faked libstdc++.so for non-x86-gcc2. For x86_gcc2, we still build libstdc++.so from the sources in the Haiku source tree as part of the Haiku build . * Put gcc_syslibs package onto the image, when needed.
|
#
be06c5a53ceac9ccceadff3efe6c6016f7bebf9b |
|
26-Mar-2012 |
François Revol <revol@free.fr> |
Build fix Reuse haiku-utils_rsrc jam var from upper Jamfile.
|
#
a59d56fa3688bf331859d4d03273490c7b7b1bef |
|
26-Mar-2012 |
François Revol <revol@free.fr> |
gcc4 build fixes.
|
#
647cff2e5925f2a1483b94aaff5620647ddf11bd |
|
26-Mar-2012 |
Axel Dörfler <axeld@pinc-software.de> |
Imported BFS-Tools (without docs), added bfsinfo to the image. * The sources are unchanged, and most of it doesn't follow Haiku's coding style -- stuff that I updated over the years might also have seen a coding style update. * This was also the basis on which Haiku's BFS has been written. * In the long run, the stuff in 'lib' that is already part of BFS should be removed, and used directly from BFS itself. * I haven't yet added any other of the tools to the image. Not sure if they are ready for inclusion yet; 'recover' could also be renamed to reflect that it is BFS specific.
|