Open Development User Group/Archive/2011-04-20
Jump to navigation
Jump to search
13:06 | Oz Linden | Hmmm.... I'm going to have to work on the Windlight settings here (trying out the project viewer - it's really gloomy here now) |
Office Orb | mail_to set to oz@lindenlab.com | |
Start transcription to oz@lindenlab.com | ||
Transcript will be sent to: oz@lindenlab.com | ||
13:07 | Oz Linden | So... our agenda is empty |
13:08 | Ima Mechanique | oops, nearly missed this |
hi all | ||
Oz Linden | I am probably going to want to cut this a little short today.... | |
Ima Mechanique | okay I can add something to the agenda ;-) | |
13:09 | Oz Linden | but we've got some time ... so what's up? |
since the agenda is empty, let's just do it | ||
Ima Mechanique | autobuild - setting a configuration in an env var... | |
Ann Otoole | must go somewhere else. good seeing everyone anyway. | |
Ima Mechanique | should that only be used if no configuration is specified? | |
13:10 | বরুনদাশ গুপ্তে | tc, Ann |
Oz Linden | the precedence is 1) command line -c switch, 2) env var, 3) default from the config file | |
বরুনদাশ গুপ্তে | that order makes sense | |
13:11 | Ima Mechanique | okay, but if it is specified as -c switch the env-var should be ignored? |
Oz Linden | correct | |
Ima Mechanique | not ran AS WELL | |
Oz Linden | right | |
Ima Mechanique | well it's not working correctly, at least on Windows | |
বরুনদাশ গুপ্তে | :-\ | |
Ima Mechanique | I haven't tracked down why yet | |
13:12 | but if I supply a different -c on the command line it runs both | |
Oz Linden | what config are you running? | |
Ima Mechanique | regardless of whether the command is configure or build | |
I have RelWithDebInfoOS set as default in env-var | ||
13:13 | Oz Linden | what if you don't specify an env var? does it still run both? |
Ima Mechanique | and I was running ReleaseOS on command line | |
if I unset the CAUTOBUILD_CONFIG_FILE it behaves normally | ||
13:14 | at first I thought it was the oops not FILE, CONFIGURATION | |
Oz Linden | wait... there are two independent things here.... | |
AUTOBUILD_CONFIG_FILE selects the file (defaults to autobuild.xml) | ||
Ima Mechanique | at first I thought it might be the CONFIG_FILE setting,I'd forggoten setting the type too | |
Oz Linden | AUTOBUILD_CONFIGURATION selects the configuration name | |
13:15 | Ima Mechanique | yes, CONFIG_FILE seems fine |
it's the default AUTOBUILD_CONFIGURATION which seems to cause the problem | ||
13:16 | only started looking through the python short while ago, so I don't know why yet | |
Oz Linden | well, I'm going to be very surprised if that's the problem | |
Ima Mechanique | well I have no idea where else to look | |
Oz Linden | but anything is possible... there is some recursion in this thing | |
13:17 | I'm not discouraging you from looking | |
good luck | ||
I'd focus on a creating a carefully documented repro | ||
Ima Mechanique | I was thinking it might be an unintended side effect of being able to run more than one configuration i.e. with --all | |
Ashiri Sands | I didn't have any idea where to look either | |
Oz Linden | it's possible | |
13:18 | I have long suspected that the windows builds do something like this (would explain why they take so long) | |
what I'm skeptical of is that the env var is part of the problem | ||
13:19 | Ima Mechanique | yeah, it was a shock to find my build hadn't finished after 90 minutes when normally it's around 60 now |
Oz Linden | unless of course they work in some odd way on Windows.... | |
Ima Mechanique | only happens it it is set, so has to be a contributing factor at least | |
13:20 | Oz Linden | like I said.... document a repro so that we can see it here |
বরুনদাশ গুপ্তে | On a related note, if you give pass-through option to 'autobuild build' after '--' and if you do not specify '--no-configure', those options are passed to both, the configuration command and the build command. | |
13:21 | Ima Mechanique | okay, will do. but there's nothing more to add I think. |
Oz Linden | not surprising | |
বরুনদাশ গুপ্তে | So, if you want to pass '-j3' to make, it'd also get passed to cmake. | |
Oz Linden | I"m not really sure that I understand why the configure step is re-run at all | |
a well-crafted bug report on that would be welcome | ||
13:22 | Ima Mechanique | it's only rerun if you've worked on your code. normal operation (for TC, etc) would be to just issue the build command |
বরুনদাশ গুপ্তে | Well, I'm not quite sure what the expected behavior would be. It looks like the configuration step is run be default to enable a complete build with a single command. | |
13:23 | Oz Linden | may be... I have not asked the developers yet |
I normally use --no-configure | ||
বরুনদাশ গুপ্তে | Maybe passing additional options should imply --no-configure | |
13:24 | or we have to separate pass-through options for the build command from pass-through options for the configure command ... | |
13:25 | Oz Linden | if someone writes up the issue, I'll try to get an answer.... |
বরুনদাশ গুপ্তে | e.g. "autobuild build -- -DLLTESTS=FALSE -- -j3" | |
ok, I'll file an issue on that, then. | ||
13:28 | Is there any chance for OPEN-38 to get pulled? | |
Office Orb | http://jira.secondlife.com/browse/OPEN-38
OPEN-38 Fixes for viewer-autobuild for standalone | |
Kadah | Oz, did your dog get in to someone's stash? He seems a little too excited out there.. or he really really loves that tree | |
13:30 | Oz Linden | I'll try to get a look next week at the various STANDALONE accomdations |
বরুনদাশ গুপ্তে | Cool, thx. | |
Oz Linden | It's going to be behind getting the contributor build farm up, though | |
13:31 | because once that's up, you can do your own test builds to see if you've busted non-standalone | |
বরুনদাশ গুপ্তে | :-) | |
Oz Linden | and I get to reduce the number of builds I do | |
Ima Mechanique | lol | |
বরুনদাশ গুপ্তে | How's that coming along, btw.? | |
13:32 | Oz Linden | Making progress.... getting the macs and the network for them set up today |
Ima Mechanique | how many machines are you getting, all told? | |
13:33 | Oz Linden | 3 macs, 1 central server to run the TeamCity build master, plus dynamic EC2 instances for the Linux and Windows builds |
Ima Mechanique | nice | |
13:34 | Kadah | Is there any documentation on the TeamCity setup? |
I toyed with it, but didn't get far | ||
Oz Linden | will probably set up things so that there are at most 3 linux builds at a time, probably 6 or 9 for windows because they are so much slower | |
Ima Mechanique | only the manuals at the Team City web site ;-) | |
Oz Linden | Once it exists, I'll put docs on the wiki | |
will need to have it up to get the names and screen shots correct | ||
13:35 | Kadah | Thanks, I'm considering setting up one for myself |
Oz Linden | most of the setup will be done for you with templates, same as we have internally | |
basically to create a build you instantiate each template and hook them together | ||
Ima Mechanique | look forward to it | |
Oz Linden | takes a few minutes, but once you have one set up it's really easy to reuse | |
13:37 | Ima Mechanique | glad to see the OPEN-50 stuff in main repo ;-) |
one tiny thing, though. ;-) | ||
Oz Linden | ? | |
13:38 | Ima Mechanique | I didn't get into the contributions.txt :-) |
Oz Linden | really? ooops | |
Ima Mechanique | that commit fell through the cracks with all the hassle that open-50 turned out to be | |
Oz Linden | I have one other thing to fix in there; will push both fixes later | |
13:39 | Ima Mechanique | no hurry |
more interested in OPEN-61 getting in ;-) | ||
13:40 | so I don't have to keep "fixing" my local repo | |
Oz Linden | one of my todo's is to fix the About box so that it gets the names from contributions.txt | |
13:41 | বরুনদাশ গুপ্তে | automatically? |
13:42 | Oz Linden | Well, at build time |
বরুনদাশ গুপ্তে | (that'd mean we have to re-compile (and re-link!) the viewer for each change in that file) | |
Zi Ree | Doesn't take long for a simple change in about. | |
Oz Linden | well, presumably you only change that file when you've changed something else.... | |
13:44 | Phoenix-FirestormViewer Rocks | well, one issue with editing about directly is you have to do it 8 or so times, one fore eash language... |
Oz Linden | I suppose I could extract the names into a file that then gets installed with the viewer and read them at run time.... | |
Zi Ree | This idea could solve it easily. | |
Oz Linden | had not worked that out | |
Phoenix-FirestormViewer Rocks | pulling from the txt file would simplify that | |
13:45 | Oz Linden | I also want to fix the fact that the icons are the same for all the viewer types (release, beta, project, development, test) |
বরুনদাশ গুপ্তে | Tankmaster, the name list is translated? That doesn't make much sense. | |
Oz Linden | I have new icons for them... just have to get them into the build | |
13:46 | Phoenix-FirestormViewer Rocks | its list of names is hard coded, at least current;y |
Zi Ree | The name list is part of other text as well, like "The following residents made it possible ..." | |
Phoenix-FirestormViewer Rocks | ^ | |
Ashiri Sands | colour-coded according to type? | |
Oz Linden | yup | |
not so clever | ||
Zi Ree | There should be a placeholder like "[CONTRIBUTORS], and [LAST_CONTRIBUTOR]". | |
Phoenix-FirestormViewer Rocks | agreed | |
13:47 | Oz Linden | the icons are not radically different, but they are distictive |
I normally have 4 installed and sometimes a 5th, so it would certainly help me | ||
13:50 | Ima Mechanique | I try to keep mine down to one of each ;-) |
one Phoenix, one, Firestorm, one v2, one v2-dev | ||
বরুনদাশ গুপ্তে | I usually start the viewer from the command line, so icons won't help me much ... | |
13:51 | Oz Linden | yeah, well, they pay me to look at a lot of release streams |
বরুনদাশ গুপ্তে | :-) | |
Ima Mechanique | I don't install the builds I do, so same about icons. Only v2 I install is the PO builds usually | |
Oz Linden | need to pack up a bit early folks... see you next time | |
Office Orb | End transcription | |
বরুনদাশ গুপ্তে | tc |