Back to home page

DOS ain't dead

Forum index page

Log in | Register

Search:  
Back to the forum
Board view  Mix view

.DXE .DLL .SO (etc.) (Developers)

posted by marcov, 19.12.2019, 20:39

> The concept of packeges in interresting. I haven't known about it before
> (although is for years used in Delphi). The main advantage is that many
> units can be grouped in one file?
You can say "this BPL/DLL contains these units". The units themselves don't change and if you don't work with BPL/DLL can be compiled normally.

IOW a package is like a DLL project, a mainprogram to build a DLL. The difference is in the metadata.

Then to use it, you have to explicitly say that you want to build a certain project with packages and list the packages to link. If you use packages, RTL is always in a package (since the other packages must link to it, so it can be shared).


> I am afraid about braking compatibility with my old code...
Packages won't be default. It is primarily useful for plugin architectures, just like DXE, just easier.

Things like IDEs use it to runtime load designtime packages and other IDE extensions.

Some RTL state will get an indirection, if you don't use it, not much changes otherwise.

> Yes, although not dynamicaly loaded I understand the possible advantage
> about changing the separate DLL modules without modifying the main EXE.
Note that this is only in the dynloaded loadlibrary case.

> I can imagine it in situation like demoversion/fullversion or "general game
> engine" / "customized game engine".
> But the important question for me is: can be this feature be switched off?
It is not even on by default. Not even in Delphi. The designtime packages you install in Delphi work via this system.

Post reply
 

Complete thread:

Back to the forum
Board view  Mix view
22752 Postings in 2119 Threads, 402 registered users (1 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum