Mirror of secondlife/3p-apr_suite (third-party build dependency for Slipstream)
  • C 90.4%
  • Makefile 3.9%
  • Shell 2.9%
  • M4 1.7%
  • Perl 0.3%
  • Other 0.6%
Find a file
TJ beedfb88f0
Merge pull request #12 from Hecklezz/fix/erroneous__attribute__definition
Fix erroneous check for __attribute__ definition
2025-10-21 13:29:23 -07:00
.github Add macOS universal lib build support 2024-11-21 17:15:22 -05:00
apr Merge pull request #12 from Hecklezz/fix/erroneous__attribute__definition 2025-10-21 13:29:23 -07:00
apr-iconv Update config.sub and config.guess 2023-12-12 18:13:32 +01:00
apr-util Add macOS universal lib build support 2024-11-21 17:15:22 -05:00
.gitignore Simplified darwin build removing unneeded autoconf contortions. 2023-02-02 14:20:22 -08:00
autobuild.xml Add macOS universal lib build support 2024-11-21 17:15:22 -05:00
build-cmd.sh Add macOS universal lib build support 2024-11-21 17:15:22 -05:00
BuildParams Fixes to bring Buildparams into line with SLING 2017-04-28 13:37:42 -07:00
README.LINDEN.WINDOWS.txt Reformat README.LINDEN.WINDOWS.txt. 2023-01-24 15:33:08 -05:00

In order to facilitate building on Windows, the APR project is distributed
with a set of Visual Studio 6 .dsw and .dsp files. Since we use a newer build
toolchain, they must first be imported and converted to the new file format
(e.g. .sln and .vcxproj for VS2010). If this autobuild package fails to build
on Windows after upgrading to a new version, it may be necessary to reimport
the newer VS6 files to pick up changes in the files that make up APR.

After importing the Visual Studio 6 .dsw files into VS2010, the link
information for each of the projects was missing. The build for libapriconv
and libaprutil failed during the link step because they depend on libapr and
other libs. In this commit, I have fixed the problem in the respective vcxproj
files, however, if this library is upgraded again and the VS6 dsw file is
imported again, it is likely that the information will be lost on import
again. The process I followed to set up the link information is below:

1. Open the aprutil.sln solution that was created by importing the aprutil.dsw
   file.

2. Right click the project you need to fix (libapriconv or libaprutil) and
   choose properties.

3. Expand VC++ Directories and edit the Library Directories line. At the end,
   append a path to the directory containing the .lib file you would like to
   link. Relative paths work.

4. Expand the linker tab in the sidebar and select input. Prepend the name of
   the .lib file you are linking.

The process above needs to be repeated for both the debug and release targets
of each library that is fixed. I chose to link the expat lib file from the
3p-expat autobuild package instead of the one generated by the xml project
included in the apr source distribution.