foundry27 : Post

Forum Topic - Include path differences between qcc 4.2.4 and 3.3.5: (2 Items)

View: as

Mark Dowdy(deleted)

06/25/2009 6:57 PM

post32552

Include path differences between qcc 4.2.4 and 3.3.5

I'm attempting to migrate our PC hosted development from 6.3.2 (qcc
3.3.5) to 6.4 (qcc 4.2.4) and I quickly hit a roadblock with the new
compiler. Our build scripts create cygwin style paths for the -I option
to qcc and it seems 4.2.4 does not support this path format. Is there a
way to use /cygdrive/c/... include paths with 4.2.4 or are we forced to
modify our build scripts to use quasi-windoze style paths (C:/... - note
drive letter but forward slash)? Thanks.

 

Mark

Ryan Mansfield(deleted)

06/25/2009 9:14 PM

post32554

Re: Include path differences between qcc 4.2.4 and 3.3.5

Mark Dowdy wrote:
> I'm attempting to migrate our PC hosted development from 6.3.2 (qcc
> 3.3.5) to 6.4 (qcc 4.2.4) and I quickly hit a roadblock with the new
> compiler. Our build scripts create cygwin style paths for the -I option
> to qcc and it seems 4.2.4 does not support this path format. Is there a
> way to use /cygdrive/c/... include paths with 4.2.4 or are we forced to
> modify our build scripts to use quasi-windoze style paths (C:/... - note
> drive letter but forward slash)? Thanks.

Starting with 6.4.0, the Windows SDK no longer uses cygwin and no the 
tools no longer support cygwin style paths.

Regards,

Ryan Mansfield

Return

The text you entered is not a valid object ID
More Information
Object IDs begin with an object prefix and end with a number. For example, if you enter
artf2345
the application will jump directly to an artifact with the ID artf2345. Some valid object prefixes are:
artf	for an artifact
doc	for a document
page	for a project page
topc	for a discussion topic
wiki	for a wiki page