C.D. Clark III
C.D. Clark III
I agree. I am doing the same thing. For my projects, I am writing recipes that just do a normal cmake install and then set the environment variable `MyProject_DIR` to...
I've been experimenting with different ways using a packages CMake Config file and I have found that this works if you have control over the recipe. ``` def package_info(self): package_path...
> Including a "config" from another config generated by conan looks weird. I agree, and we actually have a package that depends on `MyLib_DIR` being set to the correct directory,...
@thorntonryan Thanks for the correction, `builddirs` needs to be a list. And I think your right about just using `self.package_folder`, I'll start using that.
Hmmm, all good points. Perhaps it is best solved on a case-by-case basis. I am currently using a custom generator that does this, but I don't have a remote cache,...
I wrote the first implementation of the `siunitx` formatter, and you are correct, it does not do any name mapping. It just takes the string that pint calls the name...
Hi, sorry for the delay. Yes, I would. This library was started before I got an automated code formatting setup in vim/neovim.
We now have GitHub workflows for testing on Windows and Mac OS. Thank you @uilianries .
> In addition, you'd better run cppship lint and fmt in advance in your env using llvm@19. Yes, I have run both, but there were no warnings/changes ```bash on ...
> > Yes, I have run both, but there were no warnings/changes > > ```shell > cppship fmt -c HEAD~6 > cppship lint -c HEAD~6 > > # run this...