You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Thanks for using Delphinus. I noticed some things and little errors ;)
"first_version": "1.9.2.022"
That one is required if your repository already has releases which were added before supporting Delphinus. SInce there are no releases, this one is not required(and you won't need it for this repo in the future)
This does not make sense for a package without any previous releases.
Compiler_Min/Max is required to specify the supported compilers for the current version(if this differs from previous versions!).
So lets say the current version supports XE2-Berlin and previous versions supported XE too, this one will only use XE2-Berlin
Package_Compiler_Min/Max specifies all supported compilers across all released versions.
For Example if the current version supports only XE2-Berlin, but a previous version supported XE too, this setting includes XE-Berlin.
Since you have no release yet, you can simply use compile_min/max or Package_Compiler_Min/Max. This gets important when supported delphi versions change. You can remove the package_* one
And in addition you specify 22-26 but the installationfile specifies up to 31, so you have to use i.e.
"compiler_min": 22,
"compiler_max": 31
Another thing to note for the Delphinus.Install.json(and only here):
If compiler_min/max have the same value, you can simply specify
"compiler": YourValue
Raw:
"raw_folders":
[
{
"folder": "DLL"
}
],
The filestructure in "DLL" is currently incorrect. Delphinus specifies a fixed folderstructure beneath the given folder. Depending on where you want those files, you have to add them to the given folders. For example if the DLLs should reside in the Components Bin directory, you'd create a structure like this:
DLL\bin\win32\MyLib.dll
DLL\bin\win64\MyLib64.dll
The user will have to move those files manually to his project when running.
Or you could put them into the BPL directory, which will make them discoverable(since BPL directories are in the PATH variable of windows). But be VERY carefull with this. Your DLLs have no version in their name, so putting them into a folder visible by PATH might clutter/fuckup the system.
DLL\bpl\win32\MyLib.dll
DLL\bpl\win64\MyLib64.dll
The text was updated successfully, but these errors were encountered:
Hi,
Thanks for using Delphinus. I noticed some things and little errors ;)
That one is required if your repository already has releases which were added before supporting Delphinus. SInce there are no releases, this one is not required(and you won't need it for this repo in the future)
This does not make sense for a package without any previous releases.
Compiler_Min/Max is required to specify the supported compilers for the current version(if this differs from previous versions!).
So lets say the current version supports XE2-Berlin and previous versions supported XE too, this one will only use XE2-Berlin
Package_Compiler_Min/Max specifies all supported compilers across all released versions.
For Example if the current version supports only XE2-Berlin, but a previous version supported XE too, this setting includes XE-Berlin.
Since you have no release yet, you can simply use compile_min/max or Package_Compiler_Min/Max. This gets important when supported delphi versions change. You can remove the package_* one
And in addition you specify 22-26 but the installationfile specifies up to 31, so you have to use i.e.
Another thing to note for the Delphinus.Install.json(and only here):
If compiler_min/max have the same value, you can simply specify
Raw:
The filestructure in "DLL" is currently incorrect. Delphinus specifies a fixed folderstructure beneath the given folder. Depending on where you want those files, you have to add them to the given folders. For example if the DLLs should reside in the Components Bin directory, you'd create a structure like this:
The user will have to move those files manually to his project when running.
Or you could put them into the BPL directory, which will make them discoverable(since BPL directories are in the PATH variable of windows). But be VERY carefull with this. Your DLLs have no version in their name, so putting them into a folder visible by PATH might clutter/fuckup the system.
The text was updated successfully, but these errors were encountered: