Improve a Firebird compilation scripts (bat files)
--------------------------------------------------
Key: CORE-5195
URL: http://tracker.firebirdsql.org/browse/CORE-5195
Project: Firebird Core
Issue Type: Improvement
Components: Build Issues / Porting
Affects Versions: 3.0.0
Reporter: Kovalenko Dmitry
I offer to correct the "build" process for simplified a cleanup and creation
different sets of binaries.
At first time - for Windows environment.
1. Names of intermediate (temp, generated, output) directories should countains
the <compiler signature>, <configuration name>, <platform name>
For example:
<temp|gen|output>\msvc14xp_Win32_Debug
<temp|gen|output>\msvc14xp_Win32_Release
<temp|gen|output>\msvc14xp_x64_Debug
<temp|gen|output>\msvc14xp_x64_Release
2. Directories "output_Win32" and "output_x64" can contains the last compiled
binaries (copies from output directory)
3. All log files must be created in "temp\<intermediate folder>\log".
Not in "builds\win32"
4. Allow the explicit definition of version Visual Studio (msvc10, msvc11,
msvc12, msvc14 ....). By default, bat-files can use last known/supported
version.
----------
Example of implementation:
https://github.com/dmitry-lipetsk/firebirdsql-core/blob/B2_5_Release/builds/win32/build_fb_all.bat
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
