Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve a Firebird compilation scripts (bat files) [CORE5195] #5476

Open
firebird-automations opened this issue Apr 14, 2016 · 1 comment
Open

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @ibprovider

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

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

1 and 4 looks very questinable for me
2 does nothing new
3 what exact log's do you mean ?

What benefits it adds ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant