LMD VCL - DevUtil

<< Back to Getting started page

[edit]

Introduction

Customers who purchased LMD VCL Complete Subscription can request access data to our source code repository (which allows to download most current version at any time). The LMD VCL 2007 source branch is quite complex with the two main products (LMD-Tools, LMD ElPack and LMD IDE-Tools) + various sub- and standalone packages). Therefore we created a small tool which allows simple and fast testing of any possible package combination. A package combination (a set of LMD projects, e.g. LMD-Tools Core Controls + ChartPack and DesignPack) is called a WorkSpace.

Features

User with SVN can completely abstain from downloading full installers: Using the SVN sourcecode and LMD DevUtil any supported package can be easily created on the fly. Major features are:

• Apart from a first huge download (of the current source releases) only actually changed source files (or better: even source changes) need to be downloaded in the future (instead of full installers with complete sourcecode).
• Besides predefined standard WorkSpaces (which actually correspond to available LMD 2007 packages) you can set up any custom WorkSpace. You need to attend specific dependencies (e.g. all LMD Packages use shared lmd.rtl) only.
• LMD DevUtil is very flexible and allows any number of different local WorkSpaces with their own work/target folder.
• Working folder features:
  • Prepare folder for work in specified IDE (very fast, by one button click), e.g. generate package files, rename *.pas and *.dfm files (for .Net), create working project group, remove all other LMD-packages from IDE registry, add working folder to IDE search paths and start specified IDE with that project group.
  • Clear all compiled, garbage files; rename files back, delete redundant package files, ect. (useful for file comparision with main source filder).
• Setting common compiler switches via GUI

Preparations

At very first step you must ensure to get access to our source repository (based on Subversion, abbreviated: SVN). Various ways are possible (and you are free to use any available client). We strongly recommend TortoiseSVN - a great free Windows-based GUI client to access SVN based repositories. We definitely like the way how integration into Windows Explorer is done.

• URL of TortoiseSVN homepage is http://tortoisesvn.net. In the left navigation bar click on Download and get the most appropriate installer for you.
  After downloading, run the installer. If you install TortoiseSVN the first time, you usually have to reboot your system.
• Now you have to make your initial checkout for the LMD 2007 source branch. Start Windows Explorer, select a target drive and click somewhere with right mousebutton to display context menu. You will notice a new SVN Checkout... menu item. Select this menu item to display the Checkout dialog.
• Here enter the URL of the repository (you received it with your access data) and the checkout directory. We suggest to use a directory name like C:\LMD2007VCL (in any case you should avoid to select an existing directory). Then press ok.
• Ignore the message regarding a certificate, after that you will asked for username and password (which you received with your SVN access data). Now the complete and most current version of the LMD VCL 2007 sourcecode will be downloaded onto your system.

Special Note: We strongly recommend not to change any files in the local repository. Always use DevUtil to generate working/installation folders. Reason: A common sourcebase for all relevant and supported compilers is used. When you check out source directories you will notice missing project files. They will always be autogenerated on the fly when needed.

• Now start the first time LMDDevUtil.exe from the target folder.
  • A dialog will pop up and ask for the LMD VCL Source directory (usually the checkout directory, in our example: C:\LMD2007VCL) and the Root Working directory. The later one is used as variable (%ROOT_WORKDIR%) for different working directories. Mention here the target folder where compiled/generated versions should be located.
  • After that specify the name of the first WorkSpace on your system.