I tried that and it fixes one instance, but there are at least 4! I've
attached the .suo file from my working stdcxx case to the 724 JIRA. Could
you apply that and see what we get?

Thanks

Geoff.

On 29/09/06, Andrew Borley <[EMAIL PROTECTED]> wrote:

Hi Geoff,

Looks like it's the projectsvc7/tucany_sdo/tuscany_sdo.suo file that
holds this info. Unfortunately it's in some binary format which makes
management of it via svn harder as binary files don't get included in
patches. I've put it up with the Working Directory property set - let
me know if it works OK, or pass me your version & I'll commit that
instead.

Cheers
Andy



On 9/28/06, Geoffrey Winn <[EMAIL PROTECTED]> wrote:
> In JIRA 724 I contributed changes to SDO for C++ to make stdcxx a build
> option, specifically by adding new build configurations for release and
> debug builds. Unfortunately, the effect of applying that patch is to
damage
> all of the build configurations for MS VC 7.1.
>
> The problem is that before the patch was applied, all the build
> configurations set the "Working Directory" property of the Debugging
pane to
> "..\..\..\runtime\core\test". Since the patch was applied, that field is
> blank - not just in the 2 new configurations that I added, but also in
the
> two that were there before. Therefore, the tests all fail because they
are
> running in the wrong directory. My patch modified the tuscany_sdo.sln
file
> and also the sdo_runtime.vcproj and sdo_test.vcproj files. The build
tree
> that was the source of that patch does still have the Working Directory
> property set correctly and yet the current tree does not. I'm puzzled. I
> can't find where that property is stored, even in the source tree where
it
> works. Does anyone have any idea where that property is recorded because
> presumably that is the thing I need to check in to complete this change?
>
> Regards,
>
> Geoff.
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to