[Paraview] How to compile a new file???

[David E DeMarle]

Add the new file's name to the CMakeLists.txt file in its source directory.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Wed, Sep 24, 2014 at 4:07 PM, B.W.H. van Beest <bwvb at xs4all.nl> wrote:

> Hello,
>
> I'm trying to understand how ParaView's build system determines which
> files are to be compiled. The problem I encounter is that newly added
> files are not being picked-up by the makefiles. My guess is this must be
> something simple, but so far my attempts yield no result.
>
> This is what I do:
> Let's assume I'm working on a plugin, the code of which residing in
> <path_to_paraview>/ParaView/Examples/Plugins/<my_plugin_dir>
> The build directory is in <path_to_paraview>/ParaView/build.
>
> The plugin directory <my_plugin_dir> was obtained by copying and
> renaming the example plugin named "SourceToolbar".
> After that I did, in the build directory, a ccmake ..; So far, so good.
> Changes made in a source file (not in the build directory) are seen by
> make (when done in the build directory).
>
> However, when I add a new source file (<file>.cxx), I can't get
> make/cmake to add this sourcefile to the build.
> How is this supposed to work?
>
> Any help greatly appreciated.
>
>
> Kind Regards,
> Bertwim
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140924/165cc4b3/attachment.html>