What are you talking about?Ivan Denisov wrote:I have tested the command line compiler at the server side and it works well.
http://redmine.blackboxframework.org/issues/2
Why a command line compiler?
What issue are you attempting to solve?
What are you talking about?Ivan Denisov wrote:I have tested the command line compiler at the server side and it works well.
http://redmine.blackboxframework.org/issues/2
In the repository the sources of BlackBox are stored. We need some tool for compile the BlackBox from sources on the developer PC and at the server side for preparing Setup binary.DGDanforth wrote:What are you talking about?Ivan Denisov wrote:I have tested the command line compiler at the server side and it works well.
http://redmine.blackboxframework.org/issues/2
Why a command line compiler?
What issue are you attempting to solve?
This can not be done from BB GUI in the server, because server has no GUI. However we need to do this compilation for automated creation of Setup Binary.DGDanforth wrote:This should all be done within the BlackBox framework not with some add-on tool.
The BB linker creates an executable from the list of files stated by Omic. It is a trivial matter to take that list
and put it into a document and specify DevCompiler.CompileThis ....
So again I ask, what are you talking about?
Why does the 'server' need to compile anything? Should not the server simply be a file handler?Ivan Denisov wrote: This can not be done from BB GUI in the server, because server has no GUI. However we need to do this compilation for automated creation of Setup Binary.
That's rediculous! No one would get BB sources from the repository without having BlackBox to test them on.Also, when you get sources from the repository, you have no BlackBox.
Why? If you already have the interface files then you have the files. If you don't have the files then the compiler creates the sym files.There are to (sic several) ways for doing this:
1. To start BB as second directory and start Dev/Docu/Build-Tool.odc, however in this case the BlackBox will not create Sym files if interfaces was (sic were) not changed, and all the interfaces files will need to be copied manually...
Ivan, In general the process of creating files is a separate action from that of storing and retrieving files from a repository. If one (of us) builds a new version of BlackBox then it is up to that person to add those new files to their repository and then push their changes to the central repository.2. Add sources over installed BB and start Dev/Docu/Build-Tool.odc, in that case you need to copy the git folder to do not lost (sic so one does not loose the) connection with repository.
Isn't that exactly what Dev/Docu/Build-Tool.odc is?3. Make some BlackBox compiler tool (written in BlackBox) and distribute it with sources.
What do you mean by 'extra copy of BlackBox'? All of us already have a copy of BlackBox.In this case you do not need extra copy of BlackBox for the deploying development. My opinion that this is preferred variant, because this tool already done for server compilation and the developer will be sure that will be the result after the server will build Setup Binary.
I have added this two lines to BlackBox.iss for solving this problem:cfbsoftware wrote:While on the topic of version numbering both the setup.exe and / or the BlackBox.exe file should have their file properties maintained as part of the build process to identify their version number etc. You should not have to install or run an application to be able to determine what version it is. The properties of the BlackBox setup file are mostly OK except for the missing copyright notice and file version.
Code: Select all
VersionInfoVersion=1.7.0.1
AppCopyright=Copyright (c) 1994 - 2013 Oberon microsystems, Inc., Switzerland. All rights reserved.
I do not know, how to solve this problem now. There are some advices, maybe somebody has such experience?cfbsoftware wrote: However, the BlackBox exe has no proper identification at all
That is my understanding also but only an IP lawyer would be able to give you a definitive answer.Ivan Denisov wrote:Do I understand right, that the Copyright will be always owned by Oberon microsystems, Inc., while they will not present it to somebody??
As far as I know version information is associated with a Win32 application using a Win32 resource file. Usually development systems (e.g. Visual Studio, Delphi etc.) do this as part of the build process. The BlackBox DevLinker documentation statesIvan Denisov wrote:I do not know, how to solve this problem now. There are some advices, maybe somebody has such experience?cfbsoftware wrote: However, the BlackBox exe has no proper identification at all
so I believe the process for BlackBox would be:... windows resource files (.res), and type libraries (.tlb) are supported. The resource files are loaded from the Rsrc or Win/Rsrc directory.