View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0023020 | Open CASCADE | OCCT:WOK | public | 2012-03-13 13:19 | 2012-10-02 15:01 |
| Reporter | Assigned To | bugmaster | |||
| Priority | normal | Severity | minor | ||
| Status | closed | Resolution | no change required | ||
| Platform | Windows | OS | VC++ 2010 | ||
| Summary | 0023020: env_build.bat generated by wgenproj command is not usable | ||||
| Description | Due to a well-known problem with building VC++ 2010 SP1 projects from VS IDE in 64-bit mode (TRK0002 errors), env_build.bat generated by wgenproj WOK command is not usable. It is necessary to add the following lines at the end (taken from env_build.bat coming with standard OCCT 6.5.x distribution): rem Workaround for problems of building by VS2010 in 64 bit mode if /I "%VCVER%" == "vc10" ( if "%ARCH%" == "64" ( set "PATH=%VS100COMNTOOLS%..\..\VC\bin\x86_amd64;%PATH%" ) echo Attention: If you get problem during compilation with embedding manifests echo ^(mt.exe^), try buildng ^(not rebuilding^) for the second time ) Note that this correction seems suitable for building OCCT, as OCCT does not use rc.exe. However, rc.exe will still fail after this correction. | ||||
| Tags | No tags attached. | ||||
| Test case number | Test case is not required | ||||
|
|
> if "%ARCH%" == "64" ( > set "PATH=%VS100COMNTOOLS%..\..\VC\bin\x86_amd64;%PATH%" > ) > echo Attention: If you get problem during compilation with embedding manifests > echo ^(mt.exe^), try buildng ^(not rebuilding^) for the second time First, suggested workaround looks too hackish and incomplete: By the nature these changes enforces usage of cross-compiler version of build tools (can be used on 32-bit version of Windows). The proper way (to achieve the same effect) would be to call 'vcvarsall.bat' with another option: %VS100COMNTOOLS%..\..\VC\vcvarsall.bat x86_amd64 instead of: %VS100COMNTOOLS%..\..\VC\vcvarsall.bat amd64 (tested by aan). And second, this is not problem of current version of wgenproj. Now environment scripts avoid modification of LIB, INCLUDE and PATH variables as possible. Additional variables defined instead and used in VS project files. Thus building tools environment totally controlled by Visual Studio itself. |
|
|
Dear bugmaster, Please close this issue, it is no longer applicable. Generation of environment files have been tested with WOK 6.5.3 rc 5 and it works just fine. |
|
|
Problem is no longer applicable for current state of WOK |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-03-13 13:19 |
|
New Issue | |
| 2012-03-13 13:19 |
|
Assigned To | => kgv |
| 2012-03-28 15:39 | kgv | Note Added: 0020185 | |
| 2012-03-28 15:39 | kgv | Assigned To | kgv => san |
| 2012-03-28 15:39 | kgv | Status | new => feedback |
| 2012-03-29 17:29 |
|
Assigned To | san => bugmaster |
| 2012-03-29 17:30 |
|
Note Added: 0020205 | |
| 2012-03-29 17:30 |
|
Status | feedback => assigned |
| 2012-03-29 17:50 | bugmaster | Note Added: 0020207 | |
| 2012-03-29 17:50 | bugmaster | Status | assigned => closed |
| 2012-03-29 17:50 | bugmaster | Resolution | open => no change required |
| 2012-04-03 14:49 | apn | Test case number | => Test case is not required |
| 2012-10-02 15:01 | bugmaster | Project | Internal => Open CASCADE |