[MCOL-1701] Change Windows mcsapi build to use libraries from external directory Created: 2018-09-06 Updated: 2023-10-26 Resolved: 2018-09-28 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 1.1.6 |
| Fix Version/s: | 1.1.7, 1.2.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Jens Röwekamp (Inactive) | Assignee: | David Thompson (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows 10 |
||
| Sprint: | 2018-18 |
| Description |
|
Currently to build mcsapi on Windows you have to place the required libraries directly into Visual Studio's installation folder. But, once Visual Studio updates to a new version, these libraries aren't transferred to the updated directory and need to be updated manually. Therefore, it seems more desirable if we can tweak the build script to include the headers and libraries from an external directory out of the Visual Studio installation folder. |
| Comments |
| Comment by Jens Röwekamp (Inactive) [ 2018-09-26 ] |
|
Same thing applies to the included Windows C++ Redistributable that is included during the packaging process of mcsapi and mcsimport. |
| Comment by Jens Röwekamp (Inactive) [ 2018-09-27 ] |
|
Added support for external lib directory specified through the environment variable MCSAPI_BUILD_DEPENDENCY_DIR. Further changed the detection of the Microsoft Visual Studio C++ Redistributable Merge Module in the API and mcsimport. Now the path should be detected automatically after Visual Studio 2017 release updates. |
| Comment by Jens Röwekamp (Inactive) [ 2018-09-27 ] |
|
For QA:
|