I think there is a misunderstanding.
The INTRAWEB installer creates the directoy ...IntraWeb 15 and therin the directories LibD10_2W32 and LibD10_2W64, among others.
Relating to the EMBARCADERO C++Builder directory structure i would expect to get the following files also:
32-Bit development and runtime packages
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\dclIntraweb_15_D10_2.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\dclIWBootstrapD102.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\Intraweb_15_D10_2.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\IWBootstrapD102.bpl
64-Bit runtime packages
32-Bit development packages are not needed since the IDE ist a 32-Bit application.
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin64\Intraweb_15_D10_2.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin64\IWBootstrapD102.bpl
Redistributable 32Bit and 64-Bit runtime packages
C:\Program Files (x86)\Embarcadero\Studio\19.0\Redist\win32\Intraweb_15_D10_2.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\Redist\win32\IWBootstrapD102.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\Redist\win64\Intraweb_15_D10_2.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\Redist\win64\IWBootstrapD102.bpl
The 64-Bit runtime packages are missing!
The INTRAWEB installer creates only the 32-Bit development and runtime packages:
C:\Users\Public\Documents\Embarcadero\Studio\19.0\BPL\dclIntraweb_15_D10_2.bpl
C:\Users\Public\Documents\Embarcadero\Studio\19.0\BPL\dclIWBootstrapD102.bpl
C:\Users\Public\Documents\Embarcadero\Studio\19.0\BPL\Intraweb_15_D10_2.bpl
C:\Users\Public\Documents\Embarcadero\Studio\19.0\BPL\IWBootstrapD102.bpl
This is the common directory structure which is used for all customer software packages in C++ Builder 10.2.3,
including Indy for example.
Best Regards
Juergen
Yes i want to deploy with runtime packages and i do so for applications for many, many years successful.
This is also the default setting for C++Builder.
IW14 also supports runtime packages.
The INTRAWEB installer creates the directoy ...IntraWeb 15 and therin the directories LibD10_2W32 and LibD10_2W64, among others.
Relating to the EMBARCADERO C++Builder directory structure i would expect to get the following files also:
32-Bit development and runtime packages
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\dclIntraweb_15_D10_2.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\dclIWBootstrapD102.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\Intraweb_15_D10_2.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\IWBootstrapD102.bpl
64-Bit runtime packages
32-Bit development packages are not needed since the IDE ist a 32-Bit application.
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin64\Intraweb_15_D10_2.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\bin64\IWBootstrapD102.bpl
Redistributable 32Bit and 64-Bit runtime packages
C:\Program Files (x86)\Embarcadero\Studio\19.0\Redist\win32\Intraweb_15_D10_2.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\Redist\win32\IWBootstrapD102.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\Redist\win64\Intraweb_15_D10_2.bpl
C:\Program Files (x86)\Embarcadero\Studio\19.0\Redist\win64\IWBootstrapD102.bpl
The 64-Bit runtime packages are missing!
The INTRAWEB installer creates only the 32-Bit development and runtime packages:
C:\Users\Public\Documents\Embarcadero\Studio\19.0\BPL\dclIntraweb_15_D10_2.bpl
C:\Users\Public\Documents\Embarcadero\Studio\19.0\BPL\dclIWBootstrapD102.bpl
C:\Users\Public\Documents\Embarcadero\Studio\19.0\BPL\Intraweb_15_D10_2.bpl
C:\Users\Public\Documents\Embarcadero\Studio\19.0\BPL\IWBootstrapD102.bpl
This is the common directory structure which is used for all customer software packages in C++ Builder 10.2.3,
including Indy for example.
Best Regards
Juergen
(09-03-2018, 07:22 PM)Alexandre Machado Wrote:(09-03-2018, 09:09 AM)JuergenS Wrote: Yes i can compile, i just miss the 64-Bit runtime packages.
You mean you want to deploy using runtime packages? Do you have a good reason for that or is it just a personal preference? I'm asking because I'm curious. Runtime packages, in theory are great. In practice they are a nightmare.
Yes i want to deploy with runtime packages and i do so for applications for many, many years successful.
This is also the default setting for C++Builder.
IW14 also supports runtime packages.