Re: [Scons-dev] Workflow

Hi Rob, for my last bugfix (and pull request) I used Mercurial's bookmark feature successfully. I guess with your current commits the problem is that both changesets have the (implicit) branch "default", so Bitbucket can't decide what you want to do: 1) update your old pull request with addit

Re: [Scons-dev] Branching/cloning policy

On 09.08.2012 19:39, Gary Oberbrunner wrote: On Thu, Aug 9, 2012 at 1:28 PM, Russel Winder wrote: My worry with the single repository with default a mirror and a named branch is that in order to process any pull requests you have to accept the presence of the named branch in the mainline reposi

Re: [Scons-dev] Progressing D tool support

Hi Bill, On 09.08.2012 20:23, William Deegan wrote: Russel, Perhaps you we need to make a "how to setup a buildslave" page and add instructions for installing D to that page? I'll be taking a look at the buildbot today to see if I can recuperate it. I would be very interested in a smal

Re: [Scons-dev] 2.2.0 soon?

On 24.08.2012 19:03, Gary Oberbrunner wrote: On Fri, Aug 24, 2012 at 12:38 PM, Russel Winder wrote: Is this something that needs some planning and action so that it doesn't fall through the cracks? Yes, for sure. I don't have time right now to investigate it further, but if someone could at l

Re: [Scons-dev] zero pull requests

On 29.08.2012 02:36, Gary Oberbrunner wrote: We're down to zero open pull requests -- I accepted the two open ones this evening, including Dirk's reworking of the test infrastructure to support external tool testing and (my fave feature) file and dir test fixtures. And now, on to the next stag

[Scons-dev] Failing buildbot runs...

Hi, the new buildslaves are doing good work...and throw a lot of fails. ;) I'd like to open a bug for fixing a few issues, such that we can hopefully get all tests to pass again. Just wanted to check and make sure that nobody else has started to work on this. If you do, raise your hand pleas

Re: [Scons-dev] Failing buildbot runs...

Hi, On 30.08.2012 15:45, Gary Oberbrunner wrote: On Wed, Aug 29, 2012 at 6:14 PM, Dirk Bächle wrote: Hi, the new buildslaves are doing good work...and throw a lot of fails. ;) I'd like to open a bug for fixing a few issues, such that we can hopefully get all tests to pass again. Just w

Re: [Scons-dev] Tool use

Hi Russel, On 04.09.2012 07:37, Russel Winder wrote: Is anyone using PyCharm or Eclipse/PyDev to work on the SCons codebase? ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev yes, I use Eclipse/PyDev.

Re: [Scons-dev] Tests

Hi Russel, On 04.09.2012 06:54, Russel Winder wrote: Dirk's test framework uses a naming convention to distinguish test drivers from other python files. This means a set of test drivers can use shared modules which are ignored as tests. The SCons test framework treats every .py file as a test d

Re: [Scons-dev] boostrap and MANIFEST

On 06.09.2012 08:10, Russel Winder wrote: There must be a reason why the bootstrap process uses a manifest file, and that there is a text and an XML version of the same data. That reason eludes me just now but I am sure someone will enlighten me! ___

Re: [Scons-dev] Tigris

Hi there, On 15.09.2012 08:04, Russel Winder wrote: On Fri, 2012-09-14 at 09:22 -0400, Gary Oberbrunner wrote: […] Nobody really likes the Tigris tracker. There was some work to start migrating away from it a while ago (Anatoly I think?), but I think we decided to get the code over to bitbucke

[Scons-dev] RPM helper functions, where should they go?

Hi there, for fixing the current Buildbot failures I still have to fight down several RPM tests. They check the names of the created RPM files, which differ depending on the used hardware/os combination. I'd like to wrap the original RPM functions for canonicalizing machine/system names and al

Re: [Scons-dev] RPM helper functions, where should they go?

On 25.09.2012 20:03, Gary Oberbrunner wrote: On Tue, Sep 25, 2012 at 1:38 PM, Dirk Bächle wrote: Hi there, for fixing the current Buildbot failures I still have to fight down several RPM tests. They check the names of the created RPM files I think many of the current tests are way too strict

[Scons-dev] Issue 2872, Buildbot test errors

Hi there, I created a pull request for the second round of changes to get all Buildslaves completing without any failures again. We should get pretty close this time, however there is one problem left: test/TEX/biblatex.py. On the Fedora17 system, the TeX builder picks the wrong bibtex executa

Re: [Scons-dev] Issue 2872, Buildbot test errors

On 28.09.2012 01:29, William Deegan wrote: Dirk, On Sep 27, 2012, at 3:56 PM, Dirk Bächle wrote: Bill, can you please (once again) check the timeout value for the Fedora17 system builder? In the last logs I saw the default of 1200s again. This is too low, please try to switch it back to

Re: [Scons-dev] Creating an extension: where do I start?

On 29.09.2012 14:59, Left Right wrote: Hello list, I tried SCons for several projects developed by other people and I like it very much. Though, I'd like to know it better, and from the inside too. I program mostly what is related to Flash, and so I would like to have an extension that can handl

[Scons-dev] Buildslave install instructions...

+++ Quick reminder +++ Hi, I still have a text, describing my steps for setting up the latest buildslaves under Windows and Linux. I just need a Wiki page (linked from the frontpage) where I can put it... ;) Best regards, Dirk ___ Scons-dev maili

Re: [Scons-dev] How to create a builder with optional source and target parameters?

Hi Oleg, On 03.10.2012 22:10, Left Right wrote: Hello, list. I'm trying to write an extension, and here's one thing I would like to have in it: I would like to be able to call the builder without arguments at all. [...] What would be the way to do it? I mean, of course I could've copied the ent

Re: [Scons-dev] README in repository

Hi guys, On 09.10.2012 19:39, William Deegan wrote: Russel, On Oct 9, 2012, at 9:22 AM, Russel Winder wrote: I think we have to take a vote on whether to switch the read me file at the top of the repository hierarchy from plain text to a) ReStructured Text, README.rst b) Markdown, README.m

Re: [Scons-dev] Thanks!

Hi Gary, and a very big "Thanks!" to you in return, for taking the lead over this bunch of crazy SCons guys, which are all doing very good work (Hey Russel, the new SCons intro page looks awesome!). It's a real pleasure to drive this interesting and challenging project further, together with a

Re: [Scons-dev] SCons logo images

Bill, I think that's a very good idea. At least I don't see how we can lose anything by simply starting a new repo for this purpose... Regards, Dirk On 15.10.2012 00:05, William Deegan wrote: Dirk, Re: images.. It might make sense to just make a new repo for "marketing" collateral? Inclu

Re: [Scons-dev] Tests on Fedora 17

Russel, one of the Buildslaves is a Fedora 17 system, so I wonder why you still get so many fails. I added some notes about which packages I installed, to http://scons.org/wiki/InstallingBuildbotSlaves . Maybe you can have a look and compare what's needed. If things still don't work out, bu

Re: [Scons-dev] Issue 2869 - Versioned shared libraries

Hi Rob, just had a quick look at your changes...thanks a lot for taking care of this issue. On 25.10.2012 06:09, Managan, Rob wrote: I want to get some input on this issue. I created a fork for this at https://bitbucket.org/managan/scons_soname and put Eric Raymond's code into Environment.

Re: [Scons-dev] Tool order

Hi Russel, yes the order can be important, depending on which variables and Builders are touched by the Tools. If both are working on disjunct sets of settings there shouldn't be a difference though...but it's better to not rely on this. There is no enforcement rule saying that Tools always ha

Re: [Scons-dev] Early Warning: Ceylon is a pain for SCons

Hi Russel, and what exactly would be a problem for SCons when trying to build Ceylon projects? Can we extract requirements for SCons from it? Regards, Dirk On 14.11.2012 16:52, Russel Winder wrote: Remember the problems of Java for SCons. Scala of course is far, far worse. These however are

Re: [Scons-dev] Optimizing SCons...

Hi Gary, On 02.12.2012 17:58, Gary Oberbrunner wrote: This looks very interesting. Speed and memory use are two "hot button" issues for many SCons users. What does it do that would break existing projects? Is it the not storing of full paths? (When were slots introduced? 2.2? In that ca

Re: [Scons-dev] Optimizing SCons...

Hi Bill, On 04.12.2012 16:01, William Deegan wrote: [...] I think there was a user who was working on revamping the doc toolchain for SCons (Who that is is escaping me at the moment). that would be me. I still have this on my todo list and will continue working on it next, now that the te

Re: [Scons-dev] Optimizing SCons...

Hi Anatoly, On 04.12.2012 06:57, anatoly techtonik wrote: [...] It will be easier to review this on rietveld. I don't think we have reached full review state yet. As the comments and suggestions (regarding properties, for example) show, the patch still might need some work. After getting mo

Re: [Scons-dev] Run a single test

Hi Anatoly, specifying the full relative path, like in python runtest.py test/Delete.py , should work. Dirk On 20.12.2012 15:11, anatoly techtonik wrote: Am I right that there is no way to run a single test_ currently in SCons test suite? -- anatoly t. __

[Scons-dev] Extensions to the Tool subsystem...

Hello developers, based on my proposed changes to the current tests in src/test there has been some discussion about how a Tool should work. Especially in connection with the LaTeX Tool, questions like: - Do we want to have one "latex" Tool for all, or separate ones for "miktex", "texlive"

[Scons-dev] Docbook Tool as core module?

Hi there, for the new SCons doc toolchain that I'm currently working on, I'd like to use my Docbook Builder/Tool from: https://bitbucket.org/dirkbaechle/scons_docbook . In its current state it has a simple manual and tests. It basically works...but only if called from the top build directo

Re: [Scons-dev] Extensions to the Tool subsystem...

On 20.12.2012 18:51, Managan, Rob wrote: [...] Is there a similar set of paths on Windows that we should add to the default? Or is there a place to look for a path when initializing a specific tool that needs a given executable or set of executables? I'd say that, apart from guessing and prob

Re: [Scons-dev] Buildbots

On 20.12.2012 21:27, Managan, Rob wrote: [...] Not sure what is causing the MSVS failures. Changing line 1658 in src/engine/SCons/Tool/msvs.py to: if float(env['MSVS_VERSION']) >= 10.0: makes them pass successfully on my side. Not sure whether this is a proper fix though... Dirk ___

Re: [Scons-dev] 2013+ projects

Hi Gary, thanks for compiling this list...it should keep us busy for the next three years or so. ;) See my further comments below. On 27.01.2013 23:26, Gary Oberbrunner wrote: Here's my ideas about what projects are important this year (and into the future -- there's too much here for a year

Re: [Scons-dev] GSOC this year?

Hi Bill, On 28.03.2013 19:50, William Deegan wrote: All, We need to turn in the proposal by tomorrow. ... Here's some other thoughts I have: * Change SCons code to be runnable on py2.7 and py3.0 * Get SCons to work better/at all on cygwin * Change code to use more modern constructs (slots, gen

Re: [Scons-dev] Qt support

Hi all, a Qt5 Tool (as a copy of qt4.py) is listed in the ToolsIndex. I tested it quite extensively under Linux with the Qt 5.0.1/2 release candidates and got feedback from some people that it also works fine under Windows. So we basically have Qt5 support already, I can't say anything about

Re: [Scons-dev] Qt support

Sorry, clicked the "send" button too early... On 14.04.2013 23:52, Dirk Bächle wrote: Hi all, [...] The ability to easily extend the build system by writing Builders and Tools is an important feature in SCons, making it stand out from all other competitors. So we should think ab

Re: [Scons-dev] Qt support

On 15.04.2013 00:09, Gary Oberbrunner wrote: Dirk makes a very good point, one we've thought about for a long time. It might be a good time, as we prep for the next version, to think about a contrib system. (In any case, we should either import the Qt4/5 tools or delete the Qt3 one though.)

Re: [Scons-dev] Qt support

Hi Bill, On 15.04.2013 04:11, Bill Deegan wrote: Greetings, SCons has always been (as much as possible) a batteries include tool. For me personally, and also from many questions on the mailing list and IRC, having mainstream tools not in the core confuses users. I consider QT to be a mainstr

Re: [Scons-dev] New SCons doc toolchain...

Hi, On 26.03.2013 00:50, Dirk Bächle wrote: Hi developers, over the last weeks, I collected together all the work I'd done so far on the rewrite of the documentation toolchain in SCons. It has now reached a state where I think it's ready to get a little more public, so I pushed t

Re: [Scons-dev] New SCons doc toolchain...

Hi Gary, On 21.04.2013 23:38, Gary Oberbrunner wrote: [...] Hi, Dirk! I just cloned this on my Linux box (Ubuntu 11.10 - also tried 12.04), but running scons bootstrap.py gives errors: scons: *** [design.xml] XMLSyntaxError : Specification mandate value for attribute object, line 1, colum

Re: [Scons-dev] New SCons doc toolchain...

Gary, On 22.04.2013 02:21, Gary Oberbrunner wrote: On Sun, Apr 21, 2013 at 5:57 PM, Dirk Bächle <mailto:tshor...@gmx.de>> wrote: Hi Gary, On 21.04.2013 23 :38, Gary Oberbrunner wrote: [...] Hi, Dirk! I just cloned this on my Linux box (Ubu

Re: [Scons-dev] New SCons doc toolchain...

On 23.04.2013 18:12, Russel Winder wrote: On Mon, 2013-04-22 at 23:44 +0200, Dirk Bächle wrote: […] Make sure that you have "fop" and one of the XML Python bindings installed (lxml or libxml2)...the latter is to be preferred because it is much faster, but both should work fine n

Re: [Scons-dev] New SCons doc toolchain...

On 23.04.2013 02:28, Gary Oberbrunner wrote: Works much better now. I re-cloned and installed fop and now it builds. I do get some errors about the bricks SVG file: SEVERE: svg graphic could not be built: file:/home/user/src/scons_doc_toolchain/doc/design/titlepage/SConsBuildBricks_path.svg:

Re: [Scons-dev] New SCons doc toolchain...

Hi Russel, thanks a lot for all your comments. I won't go into detail about each one of them, but would like to say a few words in general. There still may be some quirks with fonts or layouts and "fop" is certainly not state of the art for PDF rendering...whatever. To be honest, I don't care

Re: [Scons-dev] New SCons doc toolchain...

On 28.04.2013 20:20, Gary Oberbrunner wrote: On Sun, Apr 28, 2013 at 10:06 AM, Russel Winder > wrote: Given the current system is XML based, with xml files and in files required, the new system is an improvement and should be accepted. Glad you agree, I f

Re: [Scons-dev] New SCons doc toolchain...

On 29.04.2013 00:38, Gary Oberbrunner wrote: On Sun, Apr 28, 2013 at 2:44 PM, Dirk Bächle <mailto:tshor...@gmx.de>> wrote: On 28.04.2013 20:20, Gary Oberbrunner wrote: [...] I am ready to prepare a pull request any time...if we all agree that the current sta

Re: [Scons-dev] New SCons doc toolchain...

Hi Bill, On 29.04.2013 21:51, William Deegan wrote: All, I see the following when running bootstrap.py SCons import failed. Trying to run from source directory scons: Reading SConscript files ... scons: done reading SConscript files. scons: Building targets ... scons: `.' is up to date. scons:

Re: [Scons-dev] New SCons doc toolchain...

On 29.04.2013 21:51, William Deegan wrote: All, I see the following when running bootstrap.py [...] Also I had to install the following (on ubuntu 10.04) sudo apt-get install python-libxml2 python-libxslt1 python-epydoc fop python2.6-dev Note that without the proper tools installed the b

Re: [Scons-dev] New SCons doc toolchain...

On 01.05.2013 21:30, Bill Deegan wrote: Dirk, Should you also add "fop" or the other alternative to the scons_dev_master? Thanks, Bill Isn't it in the list on your side? I can see it in my revision...and on the bitbucket commit. The "xep" renderer is a commercial one, but there is a free

Re: [Scons-dev] New SCons doc toolchain...

Hi Gour, On 09.05.2013 10:33, Gour wrote: On Tue, 26 Mar 2013 00:50:07 +0100 Dirk Bächle wrote: [...] I settled to use SCons for my PyQt project and was reading the User Manual yesterday and e.g. found that the email addresses listed are wrong (e.g. us...@scons.tigris.org) which led me to

Re: [Scons-dev] New SCons doc toolchain...

Hello Gour, On 09.05.2013 22:53, Gour wrote: On Thu, 09 May 2013 12:14:29 +0200 Dirk Bächle wrote: [...] If it's good-enough for Python project docs itself, I believe it should be for SCons as well. that's okay...but to make me believe this as well, you (or someone else) has

Re: [Scons-dev] New SCons doc toolchain...

On 10.05.2013 11:15, Gour wrote: On Thu, 09 May 2013 23:55:02 +0200 Dirk Bächle wrote: that's okay...but to make me believe this as well, you (or someone else) has to deliver actual results. ;) [...] Being a little lazy and more tight with the time atm, here I provide some reference

Re: [Scons-dev] Using SCons via bootstrap.py

Hi Russel, On 17.05.2013 19:13, Russel Winder wrote: Is anyone else finding that the bootstrap.py script no longer works? It worked for me before I went away for a short break and now after updating Debian Unstable, it is failing. I get the same behaviour with Python 2.6, 2.7 and PyPy 2.0. Trac

Re: [Scons-dev] Using SCons via bootstrap.py

On 18.05.2013 08:09, Russel Winder wrote: On Sat, 2013-05-18 at 00:57 +0200, Dirk Bächle wrote: Hi Russel, […] the bootstrap.py works fine for me, I guess because I have a "src/engine" folder. Where did yours go? ;) Still exactly where it has always been, in the repository: |>

Re: [Scons-dev] Using SCons via bootstrap.py

Hi, I started to fix bootstrap.py, such that the parseManifestLines() doesn't need os.chdir() anymore. After the rewrite, the local call "python bootstrap.py" works fine again...so far, so good. But I'm not able to figure out how to call it from a different folder. I even switched back to rev

Re: [Scons-dev] Using SCons via bootstrap.py

On 22.05.2013 22:15, Gary Oberbrunner wrote: I assume you do have a SConstruct in /home/dirk/tmp/boottest? Basically, "python .../bootstrap.py" should work just like saying "scons" except you don't have to have SCons installed. I really didn't know that, thanks for helping me out Gary. :) I

Re: [Scons-dev] [Fwd: [Scons-users] [patch] SCons fails to run in standalone mode]

Hi Russel, there is pull request #79 still pending...it's supposed to fix the issue of the broken bootstrap.py. Best regards, Dirk On 06.07.2013 10:49, Russel Winder wrote: Switching this to the Dev list. Has anyone fixed this bootstrap.py issue already? Forwarded Message

Re: [Scons-dev] [Fwd: [Scons-users] [patch] SCons fails to run in standalone mode]

Hi Rob, On 08.07.2013 16:55, Managan, Rob wrote: Does anyone else use the method of setting the environment variable SCONS_LIB_DIR as mentioned in the README.rst? I should point out that the syntax is messed up there. When testing stuff myself I just use, in the top level of the checked out sco

Re: [Scons-dev] [Fwd: [Scons-users] [patch] SCons fails to run in standalone mode]

On 08.07.2013 18:32, Managan, Rob wrote: [...] For a bash shell then the equal sign is correct but you need to change setenv to export. That is what I was trying to convey in the first email. Ahhh, okay. I got it now. Maybe we should take some action about this. Instead of all this long writ

Re: [Scons-dev] [Fwd: [Scons-users] [patch] SCons fails to run in standalone mode]

On 09.07.2013 00:53, Russel Winder wrote: On Mon, 2013-07-08 at 20:18 +0200, Dirk Bächle wrote: On 08.07.2013 18:32, Managan, Rob wrote: [...] For a bash shell then the equal sign is correct but you need to change setenv to export. That is what I was trying to convey in the first email. Ahhh

Re: [Scons-dev] Unicode support in print_tree / render_tree

Hi Remko, On 13.07.2013 09:32, Remko Tronçon wrote: Hi, I filed a bug report for --tree=... crashing if the dependency tree contains unicode characters ( http://scons.tigris.org/issues/show_bug.cgi?id=2910 ) I fixed the bug locally by calling repr() on every element in the tree (which is also d

Re: [Scons-dev] [Fwd: [Scons-users] [patch] SCons fails to run in standalone mode]

On 13.07.2013 16:53, Russel Winder wrote: On Tue, 2013-07-09 at 09:17 +0200, Dirk Bächle wrote: […] In my view, bootstrap.py is more for creating the build packages. It can also copy together a local working copy (the "bootstrap" folder), which is fine for most cases when you simp

Re: [Scons-dev] Unicode support in print_tree / render_tree

k to your issue #2910. So if you attach your testcase there, it won't get forgotten. Regards, Dirk On 13.07.2013 10:30, Remko Tronçon wrote: Hi Dirk, On 13 July 2013 10:14, Dirk Bächle wrote: Have you tried to actually compile/build stuff that uses Unicode chars in filenames?

Re: [Scons-dev] Unicode support in print_tree / render_tree

Remko, On 14.07.2013 13:46, Remko Tronçon wrote: Hi Dirk, On 14 July 2013 13:16, Dirk Bächle wrote: So it would help us a lot if you could create a simple testcase for this, which breaks with the current code but should run successfully in the end. Here's a failing case:

Re: [Scons-dev] [Fwd: [Scons-users] [patch] SCons fails to run in standalone mode]

Hi Gary, On 15.07.2013 02:57, Gary Oberbrunner wrote: I'm still here -- just working 24/7 at my day job -- soon I"ll be back to SConsing I think it's important that bootstrap.py be useful to run scons directly out of its repo checkout. I use it like that. Haven't been following the disc

Re: [Scons-dev] how should a scanner be incorporated into a custom tool

Hi Ram, On 18.07.2013 20:12, Ram Bhamidipaty wrote: Hi, I've followed the instructions in the "ToolsForFools" wiki page - it helped a lot and I have several tools that are mostly working. Unfortunately include file tracking is not working. My source files are C-like - in that they have incl

Re: [Scons-dev] [Fwd: [Scons-users] [patch] SCons fails to run in standalone mode]

Hi there, On 20.07.2013 10:24, Russel Winder wrote: On Fri, 2013-07-19 at 19:56 -0400, Gary Oberbrunner wrote: […] OK, sorry that took so long. Merged. Hope that helps. Thanks for picking up on this. Sadly, I get: |> python /home/Checkouts/Mercurial/SCons/bootstrap.py /usr/bin/python /home/

Re: [Scons-dev] Pull request to automate web-site deployment

Hi there, On 23.07.2013 21:47, Gary Oberbrunner wrote: [...] Anyone else know Fabric and care to chime in? I haven't used Fabric either, yet. As long as its usage is optional, I don't mind. Just my 2 cents. Regards, Dirk ___ Scons-dev mailing

Re: [Scons-dev] Testing non-core tools

Hi Russel, so far I always used the fixture methods from the testing framework with a relative path, like this: test.file_fixture('../../../__init__.py','site_scons/site_tools/qt4/__init__.py') (example from the qt4 Tool tests). Doesn't this work for you? There is also TestCmd::workpath(...)

Re: [Scons-dev] Testing non-core tools

On 26.07.2013 19:30, Russel Winder wrote: Problem solved: TestSCons.TestSCons() causes the chdir() so by getting the getcwd() before that I am alright. Is this "gotcha" documented anywhere? It is mentioned at http://www.scons.org/wiki/DeveloperGuide/TestingMethodology for the "Hello

Re: [Scons-dev] Testing non-core tools

...and please don't use the scons_test_framework repo for further development (just got the notice that you cloned it). The current code is in the normal SCons repo (runtest.py and QMTest). Regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.or

Re: [Scons-dev] Testing non-core tools

On 26.07.2013 19:49, Russel Winder wrote: On Fri, 2013-07-26 at 19:43 +0200, Dirk Bächle wrote: ...and please don't use the scons_test_framework repo for further development (just got the notice that you cloned it). The current code is in the normal SCons repo (runtest.py and QMTest)

Re: [Scons-dev] Testing non-core tools

On 26.07.2013 20:00, Russel Winder wrote: On Fri, 2013-07-26 at 19:55 +0200, Dirk Bächle wrote: […] Keeping all test scripts under a top-level folder "test", and adding "sconstest.skip" files where needed, should give you a start pretty quickly though. So no more sc

Re: [Scons-dev] Testing non-core tools

On 26.07.2013 20:27, Russel Winder wrote: On Fri, 2013-07-26 at 20:11 +0200, Dirk Bächle wrote: […] [...] I have a test directory in the non-core tool package. If I run "/runtest.py -a" I get: If you call the runtest.py for external tests, you have to specify the &quo

Re: [Scons-dev] Testing non-core tools

Russel, On 27.07.2013 11:45, Russel Winder wrote: On Fri, 2013-07-26 at 21:36 +0200, Dirk Bächle wrote: […] If you call the runtest.py for external tests, you have to specify the "-e" option as well. OK the -e has helped. Now I am back with: 1/1 (100.00%) /usr/bin/python -tt test

Re: [Scons-dev] Testing non-core tools

Russel, On 27.07.2013 13:00, Russel Winder wrote: […] Does this help? Yes, but… is this the right paradigm to get people writing tests for non-core tools to use? I can become happy with "yes", but I just wonder if there is an easier way. I think this would require a definition of what exactly

Re: [Scons-dev] Testing non-core tools

Russel, On 27.07.2013 14:09, Russel Winder wrote: Dirk, On Sat, 2013-07-27 at 13:30 +0200, Dirk Bächle wrote: […] My irritant here is that the test SConstruct is not the same as would be used in a real project. Given all SCons tests are effectively system tests, I tend to prefer the code of

Re: [Scons-dev] Testing non-core tools

On 27.07.2013 15:51, Russel Winder wrote: [...] But the need to specify the -e to test non-core tool packages is already a marker that they are being handled specially. Also from the above tool sources are special structures and deserve special support. Given tests must run under the test fram

[Scons-dev] Wiki hacked? Again?

Hi there, is it possible that our SCons Wiki got hacked again? I just wanted to add a link to the ToolchainRevamp page and noticed that the Roadmap shows some different content: http://www.scons.org/wiki/Roadmap Other examples: http://www.scons.org/wiki/AboutSCons http://www.scons.org

[Scons-dev] PyCon 2014!?

Hi devs, if anyone should feel like proposing a nice little SCons talk for the US PyCon 2014 ( http://us.pycon.org/2014/ ), the due date is the 15th of September (yes, this year, 2013). So go for it! And if you're thinking: "Well, why don't you apply?", here are my two main reasons: 1.) Mo

Re: [Scons-dev] SCons Wiki status: no longer read-only...

On 07.09.2013 19:39, Gary Oberbrunner wrote: I've installed an ApproveChanges plug-in for the SCons wiki (www.scons.org/wiki ). This means logged-in users can edit pages as usual, but the changes go into an approval queue. [...] This is a very good idea, thanks fo

Re: [Scons-dev] [PATCH] scons soname on OpenBSD

Hi Stefan, On 09.09.2013 19:45, Stefan Sperling wrote: On Sat, Sep 07, 2013 at 04:24:41PM -0400, Gary Oberbrunner wrote: [...] The ideal way to contribute to SCons is to fork the mercurial repo at https://bitbucket.org/scons/scons, make your change, then submit a pull request. Patches sent to

Re: [Scons-dev] scons running on py2.7 and py3.3

Hi Neal, thanks for all your efforts, trying to get SCons running with Python3. I created a diff of the (current trunk + 2to3) against your repo, please find the patch file attached. Looking at the changes, I think it might be worth a try, and compile the patch into a little fixer script of

[Scons-dev] Our plan for svn -> hg?

Hi there, sorry, but I can't seem to remember: What was our plan for migrating the rest of the old SVN repo (branches, www, ..., and stuff) to Mercurial? I'm asking because I'd be interested to have a look at the "trygrep" branch, created by David Cournapeau for issue #655. Regards, Dirk

[Scons-dev] SCons speedup and profiling results...

Hi there, a few minutes ago I added a new page to our Wiki. It's called http://scons.org/wiki/WhySconsIsNotSlow and shows a few results of the speedup and profiling experiments that I did recently. As mentioned in the "Repositories" section, you can also download the full set of results and

Re: [Scons-dev] SCons speedup and profiling results...

Hi Gary, On 26.09.2013 02:08, Gary Oberbrunner wrote: [...] I think this is excellent work! Solid analysis. I know there's been some thought given to caching subst() before; it's trickier than one might think but in many cases it should work, and it definitely speeds things up. I'm also

Re: [Scons-dev] SCons speedup and profiling results...

Hi Rupert, On 26.09.2013 09:24, rupert THURNER wrote: On Thu, Sep 26, 2013 at 8:44 AM, Dirk Bächle wrote: Hi Gary, On 26.09.2013 02:08, Gary Oberbrunner wrote: [...] what are the main things which make waf, and wonderbuild so much faster than scons? a test is here, but already a little

Re: [Scons-dev] mercurial vs. git

On 29.09.2013 20:07, Gary Oberbrunner wrote: Now that we've all been living with hg for a while, what are people's opinions on hg vs. git for SCons? I'll admit I'm much deeper into git these days and I think overall it's a better system. But I'm interested in what you all think. We could swi

Re: [Scons-dev] SCons speedup and profiling results...

On 26.09.2013 02:08, Gary Oberbrunner wrote: [...] I think this is excellent work! Solid analysis. I know there's been some thought given to caching subst() before; it's trickier than one might think but in many cases it should work, and it definitely speeds things up. I'm also impresse

Re: [Scons-dev] SCons speedup and profiling results...

Hi Johan, thanks a lot for your trying out my experimental branch. On 01.10.2013 22:00, Johan Holmberg wrote: [...] Hi! I tried your branch "reduced_memory_updated" and noticed that when I alternate between using that branch and the "default" branch from the main SCons repository, some fil

[Scons-dev] Documentation in EPUB-Format?

Hi devs, since we're now using DocBook as source format for all our documentation, it would technically be relatively easy to publish things like the MAN page or the UserGuide in EPUB format as well. The latest versions of "pandoc" (> 1.12.x) offer a DocBook reader and do a, more or less, good

Re: [Scons-dev] Working branches

Hi Russel, On 04.10.2013 19:23, Russel Winder wrote: Now we have default and python3-port as working branches, we need a workflow that ensures they are kept in sync. If python3-port is left behind, then all the work to date will have been for nought. hmmm, we probably should discuss (and then

Re: [Scons-dev] Working branches

On 04.10.2013 20:19, Gary Oberbrunner wrote: [...] Feature branches seem to be the worst part of hg IMHO. Dirk, your workflow seems OK, although a bit indirect; you could run into problems once your changes are accepted, pulling back in. Russel, would Dirk's setup work for you? Alternatively

Re: [Scons-dev] Documentation in EPUB-Format?

Hi Rob, On 05.10.2013 01:42, Managan, Rob wrote: I like the idea since I like ebooks. However, I will be honest and say that for code development I would not be too likely to use it since on my desktop machines I don't have a great epub viewers. it's more like for users starting with SCons and

Re: [Scons-dev] Documentation in EPUB-Format?

On 06.10.2013 01:24, Bill Deegan wrote: Dirk, How big are the ePub files? vs pdf.. For the full UserGuide, I currently have: PDF = 2394kB vs. EPUB = 219kB , but you have to take into account that the additional graphics for the style and the titlepage eat up a lot of space for the PDF. I

Re: [Scons-dev] Documentation in EPUB-format

Hi Andrew, On 06.10.2013 19:59, Andrew Featherstone wrote: Hi Dirk, I've actually been working on adding this to the DocBook tool. I've managed to get a simple example working, and pending a tidy up I can push this to my fork at https://bitbucket.org/ajf58/scons_docbook . I didn't find a dep

Re: [Scons-dev] Documentation in EPUB-format

Andrew, On 06.10.2013 21:07, Dirk Bächle wrote: [...] The DocBook Tool is not (yet) part of the core sources. By keeping compatibility to older SCons and Python versions, we don't force people to upgrade if they want to use the Tool. So this still makes sense, I think. sorry I ha

Re: [Scons-dev] Documentation in EPUB-format

Andrew, thanks for the update on your progress. Sounds good so far... On 09.10.2013 00:26, Andrew Featherstone wrote: Hi Dirk, Yes my tool takes care of zipping up and formatting the container correctly. Unfortunately the SCons Zip builder method doesn't support source files with different c

Re: [Scons-dev] Documentation in EPUB-format

Andrew, On 13.10.2013 20:50, Andrew Featherstone wrote: [...] Dirk: I've pushed what I've got so far to https://bitbucket.org/ajf58/scons_docbook/branch/epub . I've run a basic Docbook through it and generated an EPUB file that passes the validation test here http://validator.idpf.org/ . In

  1   2   3   4   5   6   >