在存储库(SVN)中包括Delphi类型库吗? [英] Including Delphi Type Libraries in repository (SVN)?

问题描述

在SVN中保存Delphi类型库的最佳方法是什么.

What is the best way to save a Delphi Type Library in SVN.

每次编译应用程序时文件都会更改

The file changes every time you compile the Application

该文件未以可读的AscII格式保存

The file is not saved in a readable form of AscII

很难弄清从一个版本到下一个版本所做的更改

It is very difficult to work out what changes have been made from one version to the next

当多个人更改文件时，这是一个主要问题

问题:

1)是否应该将导出的"IDL"文件保存在版本控制中?

1) Should one save an exported ‘IDL’ file in the version control ?

2)可以将一个"IDL"隐藏到Delphi类型库中吗?

2) Can one covert an ‘IDL ’ into a Delphi type library If so how ?

3)使用Delphi类型库时的最佳实践是什么?

3) What are the best practices when working with a Delphi type library ?

4)在Delphi2009 datasnap项目中摆脱类型库有多容易?

4) How easy is it get rid of the type library in Delphi2009 datasnap project?

p.s.我正在使用BDS2006

p.s. I am using BDS2006

推荐答案

在Delphi 2009之前，我不会签入TLB文件，而是手动将TLB(和* _TLB.PAS文件作为参考)放入一个zip文件中，然后强制将其纳入版本控制.每当我对TLB进行实际更改时，我都会更新zip文件并将其检入.版本控制系统始终对本地TLB进行读/写和忽略.当TLB文件神秘地不再编译时，此方案为我节省了数倍的时间，我可以关闭我的项目，从zip文件解压缩，重新加载项目并继续工作.

Prior to Delphi 2009, I would not check in the TLB file but manually put the TLB (and *_TLB.PAS file for reference) into a zip file then force that into version control. When ever I made actual changes to the TLB, I would update the zip file and check it in. The local TLB was always made read/write and ignored by the version control system. This scheme saved me several times when the TLB file would mysteriously no longer compile, I could just close my project, unzip from the zip file, reload the project and continue working.

这篇关于在存储库(SVN)中包括Delphi类型库吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！