- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
I have recently made the switch to DevStudio .NET for the primary purpose of using IVF. So far, so good!
The docs for DevStudio .NET 2002 say that support for exporting makefiles has been eliminated. Swell. So much for easily diffing build configs.
The good news is, the new project files are not only human-readable, they seem to be readily parsable XML. Cool.
But wait. The IVF compiler and linker flags appear (Please correct me!) to be neither the short nor long forms of the CLI flags. Instead, the project files seem to be using nice descriptive names for the flags. That is welcome, especially if I have a mapping back to the CLI flags. Is this mapping documented?
Thanks
The docs for DevStudio .NET 2002 say that support for exporting makefiles has been eliminated. Swell. So much for easily diffing build configs.
The good news is, the new project files are not only human-readable, they seem to be readily parsable XML. Cool.
But wait. The IVF compiler and linker flags appear (Please correct me!) to be neither the short nor long forms of the CLI flags. Instead, the project files seem to be using nice descriptive names for the flags. That is welcome, especially if I have a mapping back to the CLI flags. Is this mapping documented?
Thanks
コピーされたリンク
2 返答(返信)
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
sblionel wrote:
No, it isn't. Sorry.
That's disappointing. I will log it with Premier Support.
Thanks.