Michele Regarding SVN: We don't use SVN any more for Cactus, we switched to git. The relevant repositories are now hosted on Bitbucket (which is similar to Github). To make a change, you would fork the repository there, commit the changes, and then open a pull request.
Regarding access to the Cactus wiki you mentioned in another email: Sorry about this. Someone should have gotten back to you about this by now. I cc Frank Löffler, who is located at LSU and may be able to track down the issue. However, in this day and age we may just host the wiki on Bitbucket as well, where user management is much simplified. -erik > On Mar 28, 2015, at 15:41 , Michele Mottini <[email protected]> wrote: > > I am putting together more detailed instructions, I'll add them to the > Einstein Toolkit wiki > > I managed to change the known_architectures/cygwin file so that it works with > the current Cygwin version (at least for C and C++). Is there a way I can > update it in the svn repo? (README.Windows should be changed as well probably) > > There is also a small error in CommOverloadable.h that cause some compiler > warning when using gcc, but I am not sure on how to fix it > > Thanks > > Cheers > > - Michele > > On Fri, Mar 27, 2015 at 12:00 PM, Erik Schnetter <[email protected]> > wrote: > Michele > > To my knowledge, people haven't run Cactus under Windows for a long time. I > suggest to remove all the Windows bits and start from scratch, as you did. > > Can you point us to more information (or maybe add a page to the Einstein > Toolkit wiki <https://docs.einsteintoolkit.org/et-docs/Main_Page>?) that > explains what software needs to be installed to a basic Windows system before > one can compile Cactus this way? If we want to support Windows, then it > should be easy for others to follow your steps. I have a Windows desktop at > work; if it's not too complicated, I may just try things there as well. In > the end, we should then test Windows automatically and regularly. > > -erik > > > On Mar 24, 2015, at 18:46 , Michele Mottini <[email protected]> > > wrote: > > > > Running Cactus under Windows 8.1 using Cygwin did not work 'out of the box' > > for me. The cygwin known architecture file appears to be very old (1999), > > that might explain the problems. > > > > I managed to compile and run the WaveToyC sample as follows: > > > > - remove cygwin from lib/make/known-architectures > > > > - create a Cygwin.conf specifying C/C++ compiler and linker (attached) > > > > - create a WaveToyC.th thorn file listing only the thorns needed by > > WaveToyC (attached) > > > > - create the configuration: > > > > make wave-config options=Cygwin.conf THORNLIST=WaveToyC.th > > > > - compile it: > > > > make wave > > > > - run: > > > > exe/cactus_wave.exe arrangements/CactusWave/WaveToyC/par/wavetoy.par > > > > > > This should work for all C and C++ thorns, I am not sure about the Fortran > > ones > > > > - Michele > > <Cygwin.conf><WaveToyC.th>_______________________________________________ > > Developers mailing list > > [email protected] > > http://www.cactuscode.org/mailman/listinfo/developers > > -- > Erik Schnetter <[email protected]> > http://www.perimeterinstitute.ca/personal/eschnetter/ > > My email is as private as my paper mail. I therefore support encrypting > and signing email messages. Get my PGP key from https://sks-keyservers.net. > > -- Erik Schnetter <[email protected]> http://www.perimeterinstitute.ca/personal/eschnetter/ My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from https://sks-keyservers.net.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Developers mailing list [email protected] http://www.cactuscode.org/mailman/listinfo/developers
