"Build Delphi" action doesn't support $(MSBuildProjectName)

FinalBuilder Bugs
1

Hi,


I noticed that “Build Delphi” action doesn’t support $(MSBuildProjectName) variable.


I’m using this variable to separate dcu output directories by building exe like below.


&ltDCC_DcuOutput&gt_dcu<b>$(MSBuildProjectName)$(Platform)$(Config)&lt/DCC_DcuOutput&gt



I prefer above one to below one.



&ltDCC_DcuOutput&gt_dcu<b>ActualProjectName$(Platform)$(Config)&lt/DCC_DcuOutput&gt



Both Delphi IDE & msbuild support this variable.



I understand it’s tough to support all MSBuild variables available while building delphi,


but could you support basic variable like $(MSBuildProjectName) ?


# I don’t know other “basic” variable exists

2

We don’t support MSBuild variables for the Delphi action because we don’t use MSBuild for delphi.

FinalBuilder supports delphi 3 to XE3, not all versions had MSbuild support, and in any event the MSBuild support is not very stable.

3

Posted By Vincent Parrett on 27 Feb 2013 06:10 AM

We don't support MSBuild variables for the Delphi action because we don't use MSBuild for delphi.



Hmm..

"Build Delphi" doesn't use MSBuild, but the variables like $(Platform),$(Config) is supported.

These variable are also MSBuild variables.
4

Posted By Vincent Parrett on 27 Feb 2013 06:10 AM
We don't support MSBuild variables for the Delphi action because we don't use MSBuild for delphi.


I misunderstood about variables and I confirmed you are right.
Build delphi action ignores all MSBuild variablesin dcu,etc's path output settings.

(It doesn't produce any warnings ! just produce dcu to the default destination (same folder as .pas exists)...)


I'm not satisfied about this implementation, even I feel it's annoying I'll repost about this there.

5

You can use the same settings as the delphi IDE. On the Delphi action Project tab, there are options to load the settings from the delphi project file (dproj). You can control which settings are loaded.

6

You can use the same settings as the delphi IDE. On the Delphi action Project tab, there are options to load the settings from the delphi project file (dproj). You can control which settings are loaded.


Mmm, I already uses this setting.

I can't share Directories settings if I use MSBuild variables like $(Platform), $(Config) on the IDE(dproj).

I must uncheck Directories check box and I always have to override dproj's directories settings.

(Oh, I wish I had "Use Aliases from Project Settings File" ...)


Recent delphi uses these MSBuild variables by default.

I think it's reasonable to support basic variables like Platform, Config, at least...

You already have "Platform", "Project Config" setting on Project tab.

7

I must uncheck Directories check box and I always have to override dproj's directories settings.


I tried to override dcu output settings, but failed.

What settings / logs I should check ?


Plaese see the following screen shot.

https://www.sugarsync.com/pf/D743662_60057497_064784


It creates .dcu on the same location as .pas exists.

8

You can emulate the MSBuild variables, just declare them as FinalBuilder project variables and provide the values you want for them.