Ошибка c1083 visual studio
I'm using MSVC 2010 (Express) on an ASUS desktop box (Intel Core i7-3770, (running at 3.4 GHz with 8 GB memory) using Win 7 Pro including Service Pack 1
Included libraries are dcmtk-3.5.4 (dicom toolkit), itk-4.4.2 (Insight toolkit), vtk-5.0.2 (visulizationtoolkit) and qt-4.6.3(cross platform app framework)
For some reason, MSVC intellisense CANNOT resolve that include.
4>Task "CL" (TaskId:36)
4> Environment Variables passed to tool: (TaskId:36)
4> VS_UNICODE_OUTPUT=1048 (TaskId:36)
4> Tracking command: (TaskId:36)
4> C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools\Tracker.exe /d C:\Windows\Microsoft.NET\Framework\v4.0.30319\FileTracker.dll /i C:\CVUS_Proj_New\ws-bin\QTUSViewer.dir\Release /r "C:\CVUS_PROJ_NEW\WORKSTATION\SRC\BINSERIES.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\DICOMSERIES.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\EDITFUSIONSETTINGSDIALOG.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\FUSEDSERIES.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\LINEARMEASURELINE.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\LOGGING.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\MAIN.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\MAINSCREEN.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\SEGMENTATION.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\SELECTDATABASEDIALOG.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\SELECTSERIESDIALOG.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\SERIES.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\SETTINGS.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\SETTINGSDIALOG.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\STUDY.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\STUDYDATABASE.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\STUDYLIST.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\TOOLDIALOG.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\TOOLWIDGETROI.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\TOOLWIDGETSEGMENT.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\VIEWPORT.CPP|C:\CVUS_PROJ_NEW\WORKSTATION\SRC\VIEWSEGMENT.CPP|C:\CVUS_PROJ_NEW\WS-BIN\QRC_RESOURCES.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_BINSERIES.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_DICOMSERIES.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_EDITFUSIONSETTINGSDIALOG.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_FUSEDSERIES.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_IMPORTSCANPROGRESS.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_MAINSCREEN.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_SEGMENTATION.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_SELECTDATABASEDIALOG.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_SELECTSERIESDIALOG.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_SERIES.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_SETTINGSDIALOG.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_STUDY.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_STUDYLIST.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_TOOLDIALOG.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_TOOLWIDGETROI.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_TOOLWIDGETSEGMENT.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_VIEWPORT.CXX|C:\CVUS_PROJ_NEW\WS-BIN\SRC\MOC_VIEWSEGMENT.CXX" /b MSBuildConsole_CancelEvent899f18174af14ea0a9765000dabd6662 /c "c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\CL.exe" /c /I"C:/CVUS_Proj_New/ws-bin/ITKIOFactoryRegistration" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Video/Filtering/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Video/IO/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Video/Core/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Nonunit/Review/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Registration/RegistrationMethodsv4/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Registration/Metricsv4/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Numerics/Optimizersv4/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/LevelSetsv4/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/Watersheds/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/Voronoi/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Bridge/VTK/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/SpatialFunction/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/RegionGrowing/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/QuadEdgeMeshFiltering/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Numerics/NeuralNetworks/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/MarkovRandomFieldsClassifiers/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/LabelVoting/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/KLMRegionGrowing/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageFusion/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/TransformMatlab/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/TransformInsightLegacy/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/TransformHDF5/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/TransformBase/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/RAW/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/HDF5/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/Siemens/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/GE/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/IPL/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/CSV/include" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/HDF5/src" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/HDF5/src" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/GPUThresholding/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/GPUSmoothing/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Registration/GPUPDEDeformable/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Registration/GPUCommon/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/GPUImageFilterBase/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/GPUAnisotropicSmoothing/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/GPUFiniteDifference/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/GPUCommon/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/Mesh/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/GIFTI/src/gifticlib" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Registration/FEM/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Registration/PDEDeformable/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Numerics/FEM/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Registration/Common/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/SpatialObjects/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/XML/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Numerics/Eigen/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/DisplacementField/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/DiffusionTensorImage/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/Denoising/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/DeformableMesh/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/Deconvolution/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/DICOMParser/src/DICOMParser" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/DICOMParser/src/DICOMParser" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/Convolution/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/FFT/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/Colormap/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/Classifiers/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/BioCell/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/BiasCorrection/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Numerics/Polynomials/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/AntiAlias/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/LevelSets/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/SignedDistanceFunction/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Numerics/Optimizers/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageFeature/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageSources/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageGradient/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/Smoothing/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageCompare/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/FastMarching/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/QuadEdgeMesh/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/DistanceMap/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Numerics/NarrowBand/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/BinaryMathematicalMorphology/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/LabelMap/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/MathematicalMorphology/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Segmentation/ConnectedComponents/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/Thresholding/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageLabel/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageIntensity/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/Path/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageStatistics/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/SpatialObjects/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/Mesh/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageCompose/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/TestKernel/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/VTK/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/Stimulate/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/PNG/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/PNG/src" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/PNG/src" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/NRRD/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/NrrdIO/src/NrrdIO" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/NrrdIO/src/NrrdIO" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/NIFTI/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/NIFTI/src/nifti/znzlib" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/NIFTI/src/nifti/niftilib" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/Meta/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/MetaIO/src/MetaIO" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/MetaIO/src/MetaIO" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/LSM/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/TIFF/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/TIFF/src" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/TIFF/src/itktiff" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/TIFF/src" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/JPEG/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/JPEG/src" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/JPEG/src" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/GIPL/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/GDCM/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/GDCM/src/gdcm/Source/DataStructureAndEncodingDefinition" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/GDCM/src/gdcm/Source/MessageExchangeDefinition" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/GDCM/src/gdcm/Source/InformationObjectDefinition" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/GDCM/src/gdcm/Source/Common" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/GDCM/src/gdcm/Source/DataDictionary" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/GDCM/src/gdcm/Source/MediaStorageAndFileFormat" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/GDCM/src/gdcm/Source/Common" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/GDCM" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/ZLIB/src" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/ZLIB/src" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/OpenJPEG/src/openjpeg" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/OpenJPEG/src/openjpeg" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/Expat/src/expat" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/Expat/src/expat" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/BioRad/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/BMP/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/IO/ImageBase/include" /I"C:/CVUS_Proj_New/itk-bin/Modules/IO/ImageBase" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/AnisotropicSmoothing/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageGrid/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/ImageFunction/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/Transform/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Numerics/Statistics/include" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/Netlib" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/ImageAdaptors/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/CurvatureFlow/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Filtering/ImageFilterBase/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/FiniteDifference/include" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/Core/Common/include" /I"C:/CVUS_Proj_New/itk-bin/Modules/Core/Common" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/VNLInstantiation/include" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/VNL/src/vxl/core" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/VNL/src/vxl/vcl" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/VNL/src/vxl/v3p/netlib" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/VNL/src/vxl/core" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/VNL/src/vxl/vcl" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/VNL/src/vxl/v3p/netlib" /I"C:/CVUS_Proj_New/itk-bin/Modules/ThirdParty/KWSys/src" /I"C:/CVUS_Proj_New/itk-4.4.2/Modules/ThirdParty/DoubleConversion/src/double-conversion" /I"C:/CVUS_Proj_New/vtk-bin" /I"C:/CVUS_Proj_New/vtk-bin/Utilities" /I"C:/CVUS_Proj_New/vtk-bin/VolumeRendering" /I"C:/CVUS_Proj_New/vtk-bin/Rendering" /I"C:/CVUS_Proj_New/vtk-5.0.2/VolumeRendering" /I"C:/CVUS_Proj_New/vtk-5.0.2/Hybrid" /I"C:/CVUS_Proj_New/vtk-5.0.2/Widgets" /I"C:/CVUS_Proj_New/vtk-5.0.2/Rendering" /I"C:/CVUS_Proj_New/vtk-5.0.2/Rendering/Testing/Cxx" /I"C:/CVUS_Proj_New/vtk-5.0.2/IO" /I"C:/CVUS_Proj_New/vtk-5.0.2/Imaging" /I"C:/CVUS_Proj_New/vtk-5.0.2/Graphics" /I"C:/CVUS_Proj_New/vtk-5.0.2/GenericFiltering" /I"C:/CVUS_Proj_New/vtk-5.0.2/Filtering" /I"C:/CVUS_Proj_New/vtk-5.0.2/Common" /I"C:/CVUS_Proj_New/vtk-5.0.2/Utilities" /I"C:/CVUS_Proj_New/vtk-5.0.2/Common/Testing/Cxx" /I"C:/CVUS_Proj_New/vtk-bin/Utilities/DICOMParser" /I"C:/CVUS_Proj_New/vtk-5.0.2/Utilities/DICOMParser" /I"C:/CVUS_Proj_New/vtk-bin/Utilities/vtkfreetype/include" /I"C:/CVUS_Proj_New/vtk-5.0.2/Utilities/vtkfreetype/include" /I"C:/CVUS_Proj_New/vtk-bin/Utilities/vtknetcdf" /I"C:/CVUS_Proj_New/vtk-5.0.2/Utilities/vtknetcdf" /I"C:/CVUS_Proj_New/vtk-bin/Utilities/vtkexodus2/include" /I"C:/CVUS_Proj_New/vtk-5.0.2/Utilities/vtkexodus2/include" /I"C:/CVUS_Proj_New/vtk-5.0.2/GUISupport/Qt" /I"C:/CVUS_Proj_New/qt-4.6.3/include" /I"C:/CVUS_Proj_New/qt-4.6.3/include/QtGui" /I"C:/CVUS_Proj_New/qt-4.6.3/include/QtSql" /I"C:/CVUS_Proj_New/qt-4.6.3/include/QtCore" /I"C:/CVUS_Proj_New/ws-bin" /IC:/CVUS_Proj_New/workstation /I"C:/CVUS_Proj_New/dcmtk-3.5.4/config/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/dcmdata/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/dcmimage/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/dcmimgle/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/dcmjpeg/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/dcmnet/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/dcmpstat/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/dcmqrdb/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/dcmsign/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/dcmsr/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/dcmtls/include" /I"C:/CVUS_Proj_New/dcmtk-3.5.4/ofstd/include" /nologo /W3 /WX- /O2 /Ob2 /Oy- /D WIN32 /D _WINDOWS /D NDEBUG /D _UNICODE /D UNICODE /D ITK_IO_FACTORY_REGISTER_MANAGER /D QT_DLL /D QT_GUI_LIB /D QT_SQL_LIB /D QT_CORE_LIB /D QT_NO_DEBUG /D "CMAKE_INTDIR=\"Release\"" /D _UNICODE /D UNICODE /Gm- /EHsc /MD /GS /fp:precise /Zc:wchar_t- /Zc:forScope /GR /Fo"QTUSViewer.dir\Release\\" /Fd"C:/CVUS_Proj_New/ws-bin/Release/QTUSViewer.pdb" /Gd /TP /analyze- /errorReport:prompt ..\workstation\src\main.cpp ..\workstation\src\MainScreen.cpp ..\workstation\src\Study.cpp ..\workstation\src\Series.cpp ..\workstation\src\DicomSeries.cpp ..\workstation\src\BinSeries.cpp ..\workstation\src\FusedSeries.cpp ..\workstation\src\Viewport.cpp ..\workstation\src\StudyList.cpp ..\workstation\src\SelectSeriesDialog.cpp ..\workstation\src\EditFusionSettingsDialog.cpp ..\workstation\src\SettingsDialog.cpp ..\workstation\src\LinearMeasureLine.cpp ..\workstation\src\StudyDatabase.cpp ..\workstation\src\settings.cpp ..\workstation\src\SelectDatabaseDialog.cpp ..\workstation\src\ToolDialog.cpp ..\workstation\src\ToolWidgetROI.cpp ..\workstation\src\Segmentation.cpp ..\workstation\src\ToolWidgetSegment.cpp ..\workstation\src\ViewSegment.cpp ..\workstation\src\logging.cpp src\moc_MainScreen.cxx src\moc_ImportScanProgress.cxx src\moc_Study.cxx src\moc_Series.cxx src\moc_DicomSeries.cxx src\moc_BinSeries.cxx src\moc_FusedSeries.cxx src\moc_Viewport.cxx src\moc_StudyList.cxx src\moc_SelectSeriesDialog.cxx src\moc_EditFusionSettingsDialog.cxx src\moc_SettingsDialog.cxx src\moc_SelectDatabaseDialog.cxx src\moc_ToolDialog.cxx src\moc_ToolWidgetROI.cxx src\moc_Segmentation.cxx src\moc_ToolWidgetSegment.cxx src\moc_ViewSegment.cxx qrc_resources.cxx /bigobj (TaskId:36)
4> main.cpp (TaskId:36)
3> logging.cpp (TaskId:36)
4> MainScreen.cpp (TaskId:36)
3> StudyDatabase.cpp (TaskId:36)
4> Study.cpp (TaskId:36)
3> settings.cpp (TaskId:36)
3> DatabaseSettingsDialog.cpp (TaskId:36)
4> Series.cpp (TaskId:36)
3> qtservice.cpp (TaskId:36)
3>..\workstation\src\qtservice\qtservice.cpp(426): fatal error C1083: Cannot open include file: 'qtservice.moc': No such file or directory
3> qtservice_win.cpp (TaskId:36)
3>..\workstation\src\qtservice\qtservice_win.cpp(673): fatal error C1083: Cannot open include file: 'qtservice_win.moc': No such file or directory
The compiler generates a C1083 error when it can’t find a file it requires. There are many possible causes for this error. An incorrect include search path or missing or misnamed header files are the most common causes, but other file types and issues can also cause C1083. Here are some of the common reasons why the compiler generates this error.
The specified file name is wrong
The name of a file may be mistyped. For example,
The file is not included in the include search path
this tells the compiler to look for the file in the same directory that contains the source file first, and then look in other locations specified by the build environment. If the quotation marks contain an absolute path, the compiler only looks for the file at that location. If the quotation marks contain a relative path, the compiler looks for the file in the directory relative to the source directory.
If the name is enclosed by angle brackets,
If your include files are in another directory relative to your source directory, and you use a relative path in your include directives, you must use double quotes instead of angle brackets. For example, if your header file myheader.h is in a subdirectory of your project sources named headers, then this example fails to find the file and causes C1083:
but this example works:
Third-party library issues and vcpkg
If you see this error when you are trying to configure a third-party library as part of your build, consider using vcpkg, a C++ package manager, to install and build the library. vcpkg supports a large and growing list of third-party libraries, and sets all the configuration properties and dependencies required for successful builds as part of your project.
The file is in your project, but not the include search path
To fix this issue, correct the path that the compiler uses to search for the included or imported file. A new project uses default include search paths. You may have to modify the include search path to add a directory for your project. If you are compiling on the command line, add the path to the INCLUDE environment variable or the /I compiler option to specify the path to the file.
To set the include directory path in Visual Studio, open the project’s Property Pages dialog box. Select VC++ Directories under Configuration Properties in the left pane, and then edit the Include Directories property. For more information about the per-user and per-project directories searched by the compiler in Visual Studio, see VC++ Directories Property Page. For more information about the /I compiler option, see /I (Additional Include Directories).
The command line INCLUDE or LIB environment is not set
When the compiler is invoked on the command line, environment variables are often used to specify search paths. If the search path described by the INCLUDE or LIB environment variable is not set correctly, a C1083 error can be generated. We strongly recommend using a developer command prompt shortcut to set the basic environment for command line builds. For more information, see Build C/C++ on the Command Line. For more information about how to use environment variables, see How to: Use Environment Variables in a Build.
The file may be locked or in use
If you are using another program to edit or access the file, it may have the file locked. Try closing the file in the other program. Sometimes the other program can be Visual Studio itself, if you are using parallel compilation options. If turning off the parallel build option makes the error go away, then this is the problem. Other parallel build systems can also have this issue. Be careful to set file and project dependencies so build order is correct. In some cases, consider creating an intermediate project to force build dependency order for a common file that may be built by multiple projects. Sometimes antivirus programs temporarily lock recently changed files for scanning. If possible, consider excluding your project build directories from the antivirus scanner.
The wrong version of a file name is included
The precompiled headers are not yet precompiled
When a project is configured to use precompiled headers, the relevant .pch files have to be created so that files that use the header contents can be compiled. For example, the pch.cpp file ( stdafx.cpp in Visual Studio 2017 and earlier) is automatically created in the project directory for new projects. Compile that file first to create the precompiled header files. In the typical build process design, this is done automatically. For more information, see Creating Precompiled Header Files.
Additional causes
You have installed an SDK or third-party library, but you have not opened a new developer command prompt window after the SDK or library is installed. If the SDK or library adds files to the INCLUDE path, you may need to open a new developer command prompt window to pick up these environment variable changes.
The file uses managed code, but the compiler option /clr is not specified. For more information, see /clr (Common Language Runtime Compilation).
The file is compiled by using a different /analyze compiler option setting than is used to precompile the headers. When the headers for a project are precompiled, all should use the same /analyze settings. For more information, see /analyze (Code Analysis).
The file or directory was created by the Windows Subsystem for Linux, per-directory case sensitivity is enabled, and the specified case of a path or file does not match the case of the path or file on disk.
The file, the directory, or the disk is read-only.
Visual Studio or the command line tools do not have sufficient permissions to read the file or the directory. This can happen, for example, when the project files have different ownership than the process running Visual Studio or the command line tools. Sometimes this issue can be fixed by running Visual Studio or the developer command prompt as Administrator.
There are not enough file handles. Close some applications and then recompile. This condition is unusual under typical circumstances. However, it can occur when large projects are built on a computer that has limited physical memory.
Example
The following example generates a C1083 error when the header file "test.h" does not exist in the source directory or on the include search path.
For information about how to build C/C++ projects in the IDE or on the command line, and information about setting environment variables, see Projects and build systems.
The compiler generates a C1083 error when it can’t find a file it requires. There are many possible causes for this error. An incorrect include search path or missing or misnamed header files are the most common causes, but other file types and issues can also cause C1083. Here are some of the common reasons why the compiler generates this error.
The specified file name is wrong
The name of a file may be mistyped. For example,
The file is not included in the include search path
this tells the compiler to look for the file in the same directory that contains the source file first, and then look in other locations specified by the build environment. If the quotation marks contain an absolute path, the compiler only looks for the file at that location. If the quotation marks contain a relative path, the compiler looks for the file in the directory relative to the source directory.
If the name is enclosed by angle brackets,
If your include files are in another directory relative to your source directory, and you use a relative path in your include directives, you must use double quotes instead of angle brackets. For example, if your header file myheader.h is in a subdirectory of your project sources named headers, then this example fails to find the file and causes C1083:
but this example works:
Third-party library issues and vcpkg
If you see this error when you are trying to configure a third-party library as part of your build, consider using vcpkg, a C++ package manager, to install and build the library. vcpkg supports a large and growing list of third-party libraries, and sets all the configuration properties and dependencies required for successful builds as part of your project.
The file is in your project, but not the include search path
To fix this issue, correct the path that the compiler uses to search for the included or imported file. A new project uses default include search paths. You may have to modify the include search path to add a directory for your project. If you are compiling on the command line, add the path to the INCLUDE environment variable or the /I compiler option to specify the path to the file.
To set the include directory path in Visual Studio, open the project’s Property Pages dialog box. Select VC++ Directories under Configuration Properties in the left pane, and then edit the Include Directories property. For more information about the per-user and per-project directories searched by the compiler in Visual Studio, see VC++ Directories Property Page. For more information about the /I compiler option, see /I (Additional Include Directories).
The command line INCLUDE or LIB environment is not set
When the compiler is invoked on the command line, environment variables are often used to specify search paths. If the search path described by the INCLUDE or LIB environment variable is not set correctly, a C1083 error can be generated. We strongly recommend using a developer command prompt shortcut to set the basic environment for command line builds. For more information, see Build C/C++ on the Command Line. For more information about how to use environment variables, see How to: Use Environment Variables in a Build.
The file may be locked or in use
If you are using another program to edit or access the file, it may have the file locked. Try closing the file in the other program. Sometimes the other program can be Visual Studio itself, if you are using parallel compilation options. If turning off the parallel build option makes the error go away, then this is the problem. Other parallel build systems can also have this issue. Be careful to set file and project dependencies so build order is correct. In some cases, consider creating an intermediate project to force build dependency order for a common file that may be built by multiple projects. Sometimes antivirus programs temporarily lock recently changed files for scanning. If possible, consider excluding your project build directories from the antivirus scanner.
The wrong version of a file name is included
The precompiled headers are not yet precompiled
When a project is configured to use precompiled headers, the relevant .pch files have to be created so that files that use the header contents can be compiled. For example, the pch.cpp file ( stdafx.cpp in Visual Studio 2017 and earlier) is automatically created in the project directory for new projects. Compile that file first to create the precompiled header files. In the typical build process design, this is done automatically. For more information, see Creating Precompiled Header Files.
Additional causes
You have installed an SDK or third-party library, but you have not opened a new developer command prompt window after the SDK or library is installed. If the SDK or library adds files to the INCLUDE path, you may need to open a new developer command prompt window to pick up these environment variable changes.
The file uses managed code, but the compiler option /clr is not specified. For more information, see /clr (Common Language Runtime Compilation).
The file is compiled by using a different /analyze compiler option setting than is used to precompile the headers. When the headers for a project are precompiled, all should use the same /analyze settings. For more information, see /analyze (Code Analysis).
The file or directory was created by the Windows Subsystem for Linux, per-directory case sensitivity is enabled, and the specified case of a path or file does not match the case of the path or file on disk.
The file, the directory, or the disk is read-only.
Visual Studio or the command line tools do not have sufficient permissions to read the file or the directory. This can happen, for example, when the project files have different ownership than the process running Visual Studio or the command line tools. Sometimes this issue can be fixed by running Visual Studio or the developer command prompt as Administrator.
There are not enough file handles. Close some applications and then recompile. This condition is unusual under typical circumstances. However, it can occur when large projects are built on a computer that has limited physical memory.
Example
The following example generates a C1083 error when the header file "test.h" does not exist in the source directory or on the include search path.
For information about how to build C/C++ projects in the IDE or on the command line, and information about setting environment variables, see Projects and build systems.
Компилятор создает ошибку C1083, когда не удается найти требуемый файл. Эта ошибка имеет несколько возможных причин. Наиболее распространенными причинами являются неверный путь поиска include или отсутствующие или неправильно именованные файлы заголовков, но другие типы файлов и проблемы могут также вызвать C1083. Ниже приведены некоторые распространенные причины, по которым компилятор создает эту ошибку.
Указано неверное имя файла
При вводе имени файла допущена ошибка. Например, примененная к объекту директива
может не найти файл, который вы хотели. Большинство файлов заголовков стандартной библиотеки C++ не имеют расширения h. . Чтобы устранить эту проблему, убедитесь, что указано правильное имя файла, как в следующем примере:
Файл не включен в путь поиска включаемых файлов
Это указывает компилятору искать файл в том же каталоге, который содержит исходный файл, а затем искать в других местах, заданных средой сборки. Если кавычки содержат абсолютный путь, компилятор выполняет поиск файла только в этом расположении. Если кавычки содержат относительный путь, компилятор выполняет поиск файла в каталоге относительно исходного каталога.
Если имя заключено в угловые скобки,
Если включаемые файлы находятся в другом каталоге относительно исходного каталога и в директивах Include используется относительный путь, то вместо угловых скобок следует использовать двойные кавычки. Например, если файл myheader.h заголовка находится в подкаталоге именованных заголовков проекта, в этом примере не удается найти файл и вызывается C1083:
но этот пример работает:
Проблемы с библиотекой сторонних производителей и vcpkg
если вы видите эту ошибку при попытке настроить библиотеку стороннего производителя в рамках сборки, рассмотрите возможность использования vcpkg, диспетчера пакетов C++ для установки и сборки библиотеки. vcpkg поддерживает большой и растущей список библиотек сторонних производителейи задает все свойства конфигурации и зависимости, необходимые для успешной сборки в рамках проекта.
Файл находится в проекте, но не в пути поиска включаемых файлов
Чтобы устранить эту проблему, исправьте путь, используемый компилятором для поиска включаемого или импортируемого файла. В новом проекте используются пути поиска include по умолчанию. Может потребоваться изменить путь поиска include, чтобы добавить каталог для проекта. При компиляции в командной строке добавьте путь к переменной среды include или /I параметр компилятора, чтобы указать путь к файлу.
чтобы задать путь к каталогу включения в Visual Studio, откройте диалоговое окно страницы свойств проекта. выберите VC++ каталоги в разделе свойства конфигурации в левой области, а затем измените свойство включаемые каталоги . дополнительные сведения о каталогах для отдельных пользователей и проектов, поиск которых выполняется компилятором в Visual Studio, см. в разделе страница свойств VC++ directories. Дополнительные сведения о параметре компилятора см. в /I разделе /I (дополнительные каталоги включаемых данных).
Не задана среда командной строки INCLUDE или LIB
Если компилятор вызывается из командной строки, для указания путей поиска часто используются переменные среды. Если путь поиска, описанный в переменной среды include или lib , задан неправильно, может быть сформирована ошибка C1083. Мы настоятельно рекомендуем использовать ярлык командной строки разработчика, чтобы задать базовую среду для сборок с командной строкой. Дополнительные сведения см. в разделе сборка C/C++ в командной строке. Дополнительные сведения об использовании переменных среды см. в разделе инструкции. Использование переменных среды в сборке.
Возможно, файл заблокирован или используется
Если для изменения или доступа к файлу используется другая программа, файл может быть заблокирован. Попробуйте закрыть файл в другой программе. иногда другая программа может быть Visual Studio сама по себе при использовании параметров параллельной компиляции. Если отключить параметр параллельной сборки, то эта ошибка исчезнет, а это проблема. Эта проблема также может быть вызвана другими системами параллельной сборки. Будьте внимательны при задании зависимостей файлов и проектов, чтобы порядок сборки был правильным. В некоторых случаях рекомендуется создать промежуточный проект для принудительного создания последовательности зависимостей для общего файла, который может быть создан несколькими проектами. Иногда антивирусные программы временно блокируют недавно измененные файлы для проверки. Если возможно, рассмотрите возможность исключения каталогов сборки проекта из антивирусного сканера.
Включена неправильная версия имени файла
Предкомпилированные заголовки еще не скомпилированы
Если проект настроен для использования предварительно скомпилированных заголовков, необходимо создать соответствующие .pch файлы, чтобы можно было скомпилировать файлы, использующие содержимое заголовка. например, pch.cpp файл ( stdafx.cpp в Visual Studio 2017 и более ранних версий) автоматически создается в каталоге проекта для новых проектов. Сначала необходимо скомпилировать этот файл, чтобы создать предкомпилированные файлы заголовков. В типичном проекте процесса сборки это выполняется автоматически. Дополнительные сведения см. в разделе Создание предкомпилированных файлов заголовков.
Дополнительные причины
Вы установили пакет SDK или библиотеку стороннего производителя, но после установки пакета SDK или библиотеки не открывали новое окно командной строки разработчика. Если пакет SDK или библиотека добавляет файлы в путь поиска включаемых файлов, может потребоваться открыть новое окно командной строки разработчика, чтобы получить эти изменения переменных среды.
Файл использует управляемый код, но параметр /clr компилятора не указан. Дополнительные сведения см. в разделе /clr (компиляция среды CLR).
Файл компилируется с использованием другого /analyze параметра компилятора, чем используется для предварительной компиляции заголовков. При предварительной компиляции заголовков для проекта все должны использовать одни и те же /analyze Параметры. дополнительные сведения см. в разделе /analyze (Code Analysis).
файл или каталог был создан подсистема Windows для Linux, учитывается регистр в каждом каталоге, и указанный регистр пути или файла не соответствует регистру пути или файла на диске.
Файл, каталог или диск доступен только для чтения.
Visual Studio или средства командной строки не имеют достаточных разрешений для чтения файла или каталога. это может произойти, например, когда файлы проекта имеют разные права владения, чем процесс, выполняемый Visual Studio или программ командной строки. иногда эту ошибку можно устранить, запустив Visual Studio или командную строку разработчика от имени администратора.
Недостаточно дескрипторов файлов. Закройте часть приложений и повторите компиляцию. Эта ситуация маловероятна в обычных условиях. Однако она может возникать при построении крупных проектов на компьютере с ограниченной физической памятью.
Пример
В следующем примере создается ошибка C1083, если файл "test.h" заголовка не существует в исходном каталоге или в пути поиска include.
Сведения о том, как создавать проекты C/C++ в интегрированной среде разработки или в командной строке, а также сведения о настройке переменных среды см. в разделе проекты и сборки систем.
The compiler generates a C1083 error when it can’t find a file it requires. There are many possible causes for this error. An incorrect include search path or missing or misnamed header files are the most common causes, but other file types and issues can also cause C1083. Here are some of the common reasons why the compiler generates this error.
The specified file name is wrong
The name of a file may be mistyped. For example,
The file is not included in the include search path
this tells the compiler to look for the file in the same directory that contains the source file first, and then look in other locations specified by the build environment. If the quotation marks contain an absolute path, the compiler only looks for the file at that location. If the quotation marks contain a relative path, the compiler looks for the file in the directory relative to the source directory.
If the name is enclosed by angle brackets,
If your include files are in another directory relative to your source directory, and you use a relative path in your include directives, you must use double quotes instead of angle brackets. For example, if your header file myheader.h is in a subdirectory of your project sources named headers, then this example fails to find the file and causes C1083:
but this example works:
Third-party library issues and vcpkg
If you see this error when you are trying to configure a third-party library as part of your build, consider using vcpkg, a C++ package manager, to install and build the library. vcpkg supports a large and growing list of third-party libraries, and sets all the configuration properties and dependencies required for successful builds as part of your project.
The file is in your project, but not the include search path
To fix this issue, correct the path that the compiler uses to search for the included or imported file. A new project uses default include search paths. You may have to modify the include search path to add a directory for your project. If you are compiling on the command line, add the path to the INCLUDE environment variable or the /I compiler option to specify the path to the file.
To set the include directory path in Visual Studio, open the project’s Property Pages dialog box. Select VC++ Directories under Configuration Properties in the left pane, and then edit the Include Directories property. For more information about the per-user and per-project directories searched by the compiler in Visual Studio, see VC++ Directories Property Page. For more information about the /I compiler option, see /I (Additional Include Directories).
The command line INCLUDE or LIB environment is not set
When the compiler is invoked on the command line, environment variables are often used to specify search paths. If the search path described by the INCLUDE or LIB environment variable is not set correctly, a C1083 error can be generated. We strongly recommend using a developer command prompt shortcut to set the basic environment for command line builds. For more information, see Build C/C++ on the Command Line. For more information about how to use environment variables, see How to: Use Environment Variables in a Build.
The file may be locked or in use
If you are using another program to edit or access the file, it may have the file locked. Try closing the file in the other program. Sometimes the other program can be Visual Studio itself, if you are using parallel compilation options. If turning off the parallel build option makes the error go away, then this is the problem. Other parallel build systems can also have this issue. Be careful to set file and project dependencies so build order is correct. In some cases, consider creating an intermediate project to force build dependency order for a common file that may be built by multiple projects. Sometimes antivirus programs temporarily lock recently changed files for scanning. If possible, consider excluding your project build directories from the antivirus scanner.
The wrong version of a file name is included
The precompiled headers are not yet precompiled
When a project is configured to use precompiled headers, the relevant .pch files have to be created so that files that use the header contents can be compiled. For example, the pch.cpp file ( stdafx.cpp in Visual Studio 2017 and earlier) is automatically created in the project directory for new projects. Compile that file first to create the precompiled header files. In the typical build process design, this is done automatically. For more information, see Creating Precompiled Header Files.
Additional causes
You have installed an SDK or third-party library, but you have not opened a new developer command prompt window after the SDK or library is installed. If the SDK or library adds files to the INCLUDE path, you may need to open a new developer command prompt window to pick up these environment variable changes.
The file uses managed code, but the compiler option /clr is not specified. For more information, see /clr (Common Language Runtime Compilation).
The file is compiled by using a different /analyze compiler option setting than is used to precompile the headers. When the headers for a project are precompiled, all should use the same /analyze settings. For more information, see /analyze (Code Analysis).
The file or directory was created by the Windows Subsystem for Linux, per-directory case sensitivity is enabled, and the specified case of a path or file does not match the case of the path or file on disk.
The file, the directory, or the disk is read-only.
Visual Studio or the command line tools do not have sufficient permissions to read the file or the directory. This can happen, for example, when the project files have different ownership than the process running Visual Studio or the command line tools. Sometimes this issue can be fixed by running Visual Studio or the developer command prompt as Administrator.
There are not enough file handles. Close some applications and then recompile. This condition is unusual under typical circumstances. However, it can occur when large projects are built on a computer that has limited physical memory.
Example
The following example generates a C1083 error when the header file "test.h" does not exist in the source directory or on the include search path.
For information about how to build C/C++ projects in the IDE or on the command line, and information about setting environment variables, see Projects and build systems.
Читайте также: