By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,218 Members | 1,342 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,218 IT Pros & Developers. It's quick & easy.

Generated files with attributes and absolute/relative paths

P: n/a
I have an attributed ATL project (call it B) that I am
building with Microsoft Visual C++ .NET (55537-640-3684941-
18356). In the project I include the COM generated file
A.h (from another ATL project A). The compiler interprets
this and injects the command "import A.idl" into the idl
for B. So far everything is okay. The problem is that
when I build project B in debug, it references A.idl using
the absolute path. When I build project B in release, it
references A.idl using relative addressing. The case for
release is a problem because I have other projects that
want to include B.idl, but are in a different relative
directory. My general question is if there is
documentation on how the compiler decides to use relative
or absolute paths for the files it inserts. Failing that,
does anyone know why switching from debug build to release
build would change the choice of absolute or relative
paths? (I could find no project setting related to this
issue.) Thanks for any input.
Nov 17 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.