New Release 3.5.0
We are proud to announce a new 3.5.0 release of Delphivm.
Changes to vendor
We now use a more flexible and lightweight vendor management.
- First: vendor/out is dead!!. Now, vendor binary and lib files are installed in the global out directory, like the output for your product. This way, you only have a search path for dcus, dcps etc.
-
Second: vendor is now a buiid target, like prj, but for build or make your vendor projects. Vendor projects are compiled in same order found in imports.dvm, so you can control the build order. Of course, you can pass the vendor the same options of prj. So all these are valid commands
c:\myproject> dvm vendor:make -g all c:\myproject> dvm vendor:build --ide D210 -p platform:Win32 Config:Release - This new estrategy allow you to open a project from the vendor directory and user a target you have setup in the IDE or change compiler directives.
Changes to ship
-
Now ship is also a build target, like prj. So, by default, it only build the ship for current IDE. You can pass –ide all in orde to build the zip for all IDE’s in your project. Now you can invkoe something like
c:\myproject> dvm vendor:build --ide D210 c:\myproject> dvm vendor:build --ide all -
By default, ship command don’t zip bin and lib groups. This is coherent with the above vendor estrategy. You include these groups optionally, and then the command vendorize these files in the global out, as if you just have done a vendor:build invocation.
Changes to deploy
Deploy command is now compatible with de multienvironment convenion estructure:
- c:\myproject>
+-----\RunEvn
+---\deve
+---\prod
+---\test
By default, deploys copy RunEvn\deve to out
dvmsetup.bat invocation
When you call dvm, it trys to call a file named dvmsetup.bat in your working directory. This allows configure environment variables or perform some custom task before dvm command is executed.
Other minor changes
- Fix some minor bugs
- dvm notify user if invoked from a working directory without matching IDE project files