Matches for rotor, 360 total results Sorted by newest | relevance
Fri Jan 29 21:16:26 UTC 2016 <pete_dushenski> y patches directory. should i just wait until it syncs fully and build another rotor (with line 61 updated) or is there something else i can try ?
Fri Jan 29 20:38:47 UTC 2016 <mod6> # Required Public Keys to add to your PGP Keyring. These are used to verify V, rotor, buildroot, and trinque's patch:
Fri Jan 29 20:38:25 UTC 2016 <mod6> # Required Public Keys to add to your PGP Keyring. This are used to verify V, rotor, buildroot, and trinque's patch:
Fri Jan 29 19:12:12 UTC 2016 <mod6> ok folks, my build succeeded with the changes to moving V outside of the rotor directory.
Fri Jan 29 16:35:23 UTC 2016 <mod6> ok the new script, having V outside of the rotor dir seems to be building just fine so far... will update again when its complete, or if fails.
Fri Jan 29 16:22:44 UTC 2016 <mod6> and I think this is what we want. So we can stick with that, and probably not break anything -- i'll just move V & .wot outside of the rotor dir.
Fri Jan 29 16:19:24 UTC 2016 <ascii_butugychag> this was a common complaint about my rotor system also, recall
Fri Jan 29 16:15:25 UTC 2016 <mod6> if we have V source and .wot adjacent to rotor dir, then we could press like the following:
Fri Jan 29 16:14:01 UTC 2016 <mircea_popescu> the way i see this is, script tries " mkdir -p rotor/.wot " , if it succeeds it says "wot dir created, populate and re-run please" ; if it fails it proceeds with build.
Fri Jan 29 16:13:20 UTC 2016 <mod6> the only actual alternative here is to create .wot adjacent to rotor directory, along with the V source
Fri Jan 29 16:12:51 UTC 2016 <mircea_popescu> mkdir -p rotor/.wot
Fri Jan 29 16:12:36 UTC 2016 <mod6> ok. so if we create a .wot in /.../rotor/ (so, rotor/.wot), then it can not be populated by hand...
Fri Jan 29 16:11:29 UTC 2016 <mod6> mkdir -p rotor
Fri Jan 29 16:11:29 UTC 2016 <mod6> mkdir -p rotor/toolchain
Fri Jan 29 16:02:49 UTC 2016 <mod6> make note that V does not /expect/ or /default/ to a ~/.wot dir, it just so happens in this case, that it needs to be somewhere accessable outside of the rotor build path
Fri Jan 29 16:01:14 UTC 2016 <mircea_popescu> the script ~must~ reference a .wot directory somewhere outside of the entire rotor build area. <<< wait wut ?!
Fri Jan 29 15:59:14 UTC 2016 <mod6> One notable change to the build script linked on the wiki: Since we're pressing out V in a directory that gets created by the script, there is no way to have a .wot inside this dir that it can find -- the script ~must~ reference a .wot directory somewhere outside of the entire rotor build area.
Tue Jan 26 01:36:44 UTC 2016 <mod6> TomServo: Hi, if you followed the instructions via the wiki, this means you should have built via rotor & V.
Sun Jan 24 22:38:00 UTC 2016 <BingoBoingo> polarbeard: Did rotor eat your copy too?
Sun Jan 24 10:53:37 UTC 2016 <phf> everything else in there is either cross platform clarification or straight up an #ifdef. it's a tiny ass patch, if it doesn't build on rotor, linux, etc. it's a bug in a patch