Delphinus supports Dependencies! This means as a packageauthor you can link your package to other existing ones if you require them!
Delphinus supports Dependencies! This means as a packageauthor you can link your package to other existing ones if you require them!
http://memnarch.bplaced.net/blog/2016/10/delphinus-finally-supports-dependencies/
http://memnarch.bplaced.net/blog/2016/10/delphinus-finally-supports-dependencies/
http://memnarch.bplaced.net/blog/2016/10/delphinus-finally-supports-dependencies/
http://memnarch.bplaced.net/blog/2016/10/delphinus-finally-supports-dependencies/
DCPs are usually stored in BDSCommondir\dcp
ReplyDeleteIf a thirdparty decides to do it differently, they have to add their dcp folder to the libpath of the given platform
And as a rough idea i'd do it differently. Instead of delphinus removing the requires(which can go horribly wrong) it should test for a dcp and declare a define indicating that dcp exists. The requires then must be wrapped into this define.
ReplyDeleteAlexander Benikowski I started like this, but then adding or removing a unit using project manager in the ide completely removes all ifdefs in the dpk. The require-removal is done onto a copy of the dpk, which is the one that is compiled instead of the original. Another concept I deal with is "versionitis", the bpl build/version number is also considered to require it or not
ReplyDelete