Hoi Harry On May 24, 6:51 am, Harry van der Wolf <[email protected]> wrote: > On OSX we do have a couple of text files in the build which need to be > changed to users own specific paths before you can build with XCode. > > I modified these files of course to reflect my own build environment. > > HG now commits and pushes these "changes" also on commit and push. > > unnecessary to say that I don't want this. How can I prevent this? > > Note: my work-around is now to copy the standard "SetEnv-universal.txt" and > "SetEnv-leopard.txt" to "mySetEnv-universal.txt" and "mySetEnv-leopard.txt" > and use the latter two.
Does `hg forget <PATH/TO/FILE>` work for your situation? I am not sure what the intended result is. If you want to keep general files in the repo and have user-specific files used for the build process, I would suggest integrating this in the build process, e.g. with CMake's keyword substitution like I did for Windows, e.g. with the file hugin/platforms/windows/installer/ hugin_release.iss - what is in @...@ is replaced by CMake when setting up the project. Yuv -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
