The problem is that a tool (namely, protoc.exe) isn't being run
correctly to generate the needed files. Can you to apply the attached
patch to see if that helps solve the problem? You'll have to apply it
to the 3.14.0 source code.
Utkarsh
On Thu, Mar 15, 2012 at 4:01 PM, Francisco Caraballo
<[email protected]> wrote:
> I'm getting the same error with 3.14:
> fatal error C1083: Cannot open include file: 'vtkPVMessage.pb.h': No
> such file or directory
>
> Saludos/greetings,
>
> Francisco Caraballo
>
>
>
> On Thu, Mar 15, 2012 at 6:30 PM, Utkarsh Ayachit
> <[email protected]> wrote:
>> sorry typo: I meant "unless using nmake -- which is the command line
>> build mechanism for VS"
>>
>> On Thu, Mar 15, 2012 at 12:44 PM, Francisco Caraballo
>> <[email protected]> wrote:
>>> I could try with 3.14, but I am using cmake.
>>> What do you mean with "unless using cmake".That if I am using cmake
>>> 3.14 wont work either?
>>>
>>> Saludos greetings,
>>>
>>> Francisco Caraballo
>>>
>>>
>>>
>>> On Thu, Mar 15, 2012 at 5:25 PM, Utkarsh Ayachit
>>> <[email protected]> wrote:
>>>> Any reason you're not using 3.14? I'm not sure if this is a known
>>>> issue with 3.12, but we haven't seen this with 3.14 unless using
>>>> cmake.
>>>>
>>>> Utkarsh
>>>>
>>>> On Thu, Mar 15, 2012 at 12:20 PM, Francisco Caraballo
>>>> <[email protected]> wrote:
>>>>> I build using the Visual Studio Express 2010 IDE
>>>>>
>>>>> Saludos,
>>>>>
>>>>> Francisco Caraballo
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Mar 15, 2012 at 4:46 PM, Utkarsh Ayachit
>>>>> <[email protected]> wrote:
>>>>>> How do you build? Using the visual studio IDE or command line?
>>>>>>
>>>>>> On Thu, Mar 15, 2012 at 11:33 AM, Francisco Caraballo
>>>>>> <[email protected]> wrote:
>>>>>>> I generated the project files with Cmake. I'm not using nmake, as far
>>>>>>> as I know.
>>>>>>>
>>>>>>> Saludos greetings,
>>>>>>>
>>>>>>> Francisco Caraballo
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Mar 15, 2012 at 3:40 PM, Utkarsh Ayachit
>>>>>>> <[email protected]> wrote:
>>>>>>>> Is this with nmake?
>>>>>>>>
>>>>>>>> Utkarsh
>>>>>>>>
>>>>>>>> On Thu, Mar 15, 2012 at 10:14 AM, Francisco Caraballo
>>>>>>>> <[email protected]> wrote:
>>>>>>>>> I get the following error when compiling Paraview 3.12 on Visual
>>>>>>>>> Studio Express 2010.
>>>>>>>>> << fatal error C1083: Cannot open include file: 'vtkPVMessage.pb.h':
>>>>>>>>> No such file or directory >>
>>>>>>>>>
>>>>>>>>> Following other messages on this mailing-list I gathered that this has
>>>>>>>>> something to do with Protobuf (whatever that is). So I checked the
>>>>>>>>> messages related to protobuf and found this message:
>>>>>>>>> 4>------ Build started: Project: protobuf_code_generation,
>>>>>>>>> Configuration: Release Win32 ------
>>>>>>>>> 4> Generating vtkPVMessage.pb.h, vtkPVMessage.pb.cc
>>>>>>>>>
>>>>>>>>> So in theory the file should exist, but it doesnt.
>>>>>>>>>
>>>>>>>>> Can anyone help me out with this? Is this a Paraview problem, or a
>>>>>>>>> Cmake problem, or a VS Express 2010 problem?
>>>>>>>>> I'm compiling without MPI support (because that generates a whole
>>>>>>>>> other bunch of problems) could that have something to do with my
>>>>>>>>> problem?
>>>>>>>>>
>>>>>>>>> Saludos/greetings,
>>>>>>>>>
>>>>>>>>> Francisco Caraballo
>>>>>>>>> _______________________________________________
>>>>>>>>> Powered by www.kitware.com
>>>>>>>>>
>>>>>>>>> Visit other Kitware open-source projects at
>>>>>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>>>>>
>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>>>>>> http://paraview.org/Wiki/ParaView
>>>>>>>>>
>>>>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>>>>> http://www.paraview.org/mailman/listinfo/paraview
diff --git a/CMake/ExecuteProtoC.cmake.in b/CMake/ExecuteProtoC.cmake.in
index 7c6e0f1..4270cad 100644
--- a/CMake/ExecuteProtoC.cmake.in
+++ b/CMake/ExecuteProtoC.cmake.in
@@ -19,7 +19,14 @@ else(WIN32)
set(ENV{LD_LIBRARY_PATH} ${ld_lib_path})
endif(WIN32)
+if (OutDir AND NOT OutDir STREQUAL ".")
+ set (protoc_location "@PROTOC_LOCATION_WITH_CFG@")
+else ()
+ set (protoc_location "@PROTOC_LOCATION@")
+endif()
+
+
execute_process(
- COMMAND "@PROTOC_LOCATION@" "--cpp_out=dllexport_decl=VTK_PROTOBUF_EXPORT:@CMAKE_CURRENT_BINARY_DIR@" --proto_path "@CMAKE_CURRENT_SOURCE_DIR@/Resources" "@CMAKE_CURRENT_SOURCE_DIR@/Resources/vtkPVMessage.proto"
+ COMMAND ${protoc_location} "--cpp_out=dllexport_decl=VTK_PROTOBUF_EXPORT:@CMAKE_CURRENT_BINARY_DIR@" --proto_path "@CMAKE_CURRENT_SOURCE_DIR@/Resources" "@CMAKE_CURRENT_SOURCE_DIR@/Resources/vtkPVMessage.proto"
WORKING_DIRECTORY "@CMAKE_CURRENT_BINARY_DIR@"
)
diff --git a/ParaViewCore/ServerImplementation/CMakeLists.txt b/ParaViewCore/ServerImplementation/CMakeLists.txt
index 8f85223..0fe5a39 100644
--- a/ParaViewCore/ServerImplementation/CMakeLists.txt
+++ b/ParaViewCore/ServerImplementation/CMakeLists.txt
@@ -87,11 +87,12 @@ INCLUDE_DIRECTORIES(
# Compile protobuf resources.
# run it from a script so we can set necessary paths.
get_target_property(PROTOC_LOCATION protoc_compiler LOCATION)
+set (PROTOC_LOCATION_WITH_CFG)
if (WIN32)
get_filename_component(PROTOC_DIR ${PROTOC_LOCATION} PATH)
get_filename_component(PROTOC_PDIR ${PROTOC_DIR} PATH)
get_filename_component(PROTOC_FNAME ${PROTOC_LOCATION} NAME_WE)
- set(PROTOC_LOCATION "${PROTOC_PDIR}/\${OutDir}/${PROTOC_FNAME}")
+ set(PROTOC_LOCATION_WITH_CFG "${PROTOC_PDIR}/\${OutDir}/${PROTOC_FNAME}")
endif (WIN32)
configure_file(${ParaView_CMAKE_DIR}/ExecuteProtoC.cmake.in
${CMAKE_CURRENT_BINARY_DIR}/ExecuteProtoC.cmake
@@ -100,7 +101,8 @@ add_custom_command(
OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/vtkPVMessage.pb.h
${CMAKE_CURRENT_BINARY_DIR}/vtkPVMessage.pb.cc
COMMAND ${CMAKE_COMMAND}
- ARGS -DOutDir=${CMAKE_CFG_INTDIR} -P ${CMAKE_CURRENT_BINARY_DIR}/ExecuteProtoC.cmake
+ ARGS -DOutDir:PATH=${CMAKE_CFG_INTDIR}
+ -P ${CMAKE_CURRENT_BINARY_DIR}/ExecuteProtoC.cmake
DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/Resources/vtkPVMessage.proto protoc_compiler ${ParaView_CMAKE_DIR}/ExecuteProtoC.cmake.in
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
)
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
