search for: files_matching

Samuel Williams <space.ship.traveller at gmail.com> writes: > Sorry for the rapid fire replies, but this configuration works for me: It "works" on the sense that it installs the headers, but removing the FILES_MATCHING clause changes the semantics of the command: the subsequent PATTERNs that controls which files are to be installesd becomes ineffective. > install(DIRECTORY include/ > DESTINATION include > # FILES_MATCHING > PATTERN "*.def" > PATTERN "*.h" > PATTERN...

...ar, If you review the install log I sent, you will see that the patterns still appear to work as expected. Despite that this may be a flaws in CMake, it may be prudent to see if it is possible to fix this for Mac OS X users? It may also affect other platforms? According to the documentation: The FILES_MATCHING option may be given before the first match option to disable installation of files (but not directories) not matched by any expression. I'm not sure I understand exactly what this means, but it seems to appear that it it is superfluous? Previously, it states: A PATTERN will match only complete...

Where should the specs go for code in the "lib" directory of a Rails app? I made a folder, "spec/lib/", for storing such specs, and RSpec automatically picks them up when run using "rake spec". Before I go ahead and patch rspec_on_rails/lib/autotest/ rails_rspec.rb so that autotest can monitor these specs I''d like to ask whether this is the

Sorry for the rapid fire replies, but this configuration works for me: install(DIRECTORY include/ DESTINATION include # FILES_MATCHING PATTERN "*.def" PATTERN "*.h" PATTERN "*.td" PATTERN "*.inc" PATTERN ".svn" EXCLUDE ) install(DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/include/ DESTINATION include # FILES_MATCHING PATTERN "*.def" PATTERN "*.h"...

Bleeding-edge story-writers, How are you structuring your specs? I am working on a new project and tried this: ./lib ./blah ./spec ./blah ./stories But it breaks autotest, so I moved stories parallel to lib and spec. Also what about suffixes? I have adopted "xyz_story_spec.rb", and "xyz.story" for the time being, with the line runner =

On Thu, Sep 30, 2010 at 3:08 PM, Samuel Williams <space.ship.traveller at gmail.com> wrote: > Hi, > > I might just be doing something stupid, but when I do > > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. > $ sudo make install > > I don't get the expected headers in >        /usr/local/llvm-2.8/include/llvm > > It is

Hi, I might just be doing something stupid, but when I do $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. $ sudo make install I don't get the expected headers in /usr/local/llvm-2.8/include/llvm It is simply an empty directory. What am I doing wrong? This is on Mac OS X, CMake 2.8+ Kind regards, Samuel

I''m having trouble getting autotest to run "out of the box" with rspec. I''ve got a Leopard setup with Zentest 3.5.0, rspec on trunk, and rails 2.0PR. No ".autotest" file. There are a couple of issues: 1. Running ''autotest'' inititally yields a command not found for "spec --diff unified etc etc". This seems to be an old issue but