[Scons-dev] Create textmate grammer file so we can have syntax highlighting for sconstruct/sconscript from docs?

[Bill Deegan]

Dirk,

Can we extract all the commands from the docs with the existing doc scripts?
and/or would it be fairly easy to do so?

If so we could auto generate a grammer file for editors syntax highlighting
and completion..

-Bill
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Help needed for D support in SCons on Windows

[Mats Wichmann]

On 10/08/2018 04:42 AM, Russel Winder wrote:
> On Sun, 2018-10-07 at 10:51 +, rjframe via Digitalmars-d wrote:
> […]
>>
>> I don't use SCons, but took a quick look; my current guess is that the 
>> problem is the chocolatey installation of dmd and the rest in AppVeyor; 
>> chocolatey doesn't install DMD in %SYSTEMROOT% and I don't know if the 
>> path updates take effect without restarting the shell (my own PC is too 
>> polluted to test this locally).
>>
>> Using SCons.Debug.Trace just crashes with "ValueError: I/O operation on 
>> closed file.", writing both to stdout and a file, so I haven't been able 
>> to test anything.
> 
> Thanks for taking a look into it. It seems like Chocolatey is not playing
> entirely fair.

I'll examine this further as time permits, I have the ability to spin up
clean temporary windows environments with not TOO much trouble, so I
don't have the pollution problem.

There seem to be two D environments (at least) for Windows, dmd and ldc.
The existing tests seem to have some knowledge of both, is there a
preference as to which one is more interesting to get working?

Bill is developing some new logic for locating commands on Windows which
will probably help.  At the moment the tests often do something
different than scons is going to do, which makes it a little
questionable why the tests are doing that, if the idea is to validate
scons :)


___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] should src/engine/SCons/Tool/docbook/util/* be included in the packages?

[Bill Deegan]

Assuming we could resolve the issue of locating the XSLT files installed
from native packages, how different would the namespaces be?

break everything?
Or just renamed?

On Mon, Oct 8, 2018 at 2:42 PM Dirk Bächle  wrote:

> Hi Bill,
>
>
> Am 07.10.2018 um 21:44 schrieb Bill Deegan:
> > Are the docbook xslt stylesheets we're currently including reasonably
> > available from distro's repos?
> >
>
> I haven't checked yet, but my guess is that some version would be
> offered in the major distros. But the problem is then that different
> naming schemes would be used and the folder with the stylesheets would
> be stored in random locations. This makes it difficult to provide an
> out-of-the-box experience with the Docbook Tool.
>
>
> I saw today that the actual sources of the Docbook XSLT stylesheets are
> now hosted on github too! This made me think: Maybe it would be okay to
> add another "bootstrapping step" to the Docbook Tool, where it clones
> the stylesheets from github to its local folder?
>
> Then we wouldn't have to store all the XSLT files directly in our repo.
> Our build/release workflow would get a little more complicated and users
> of the Docbook Tool would have to "init" it once on each of their
> machines. But maybe it's worth giving it a try?
>
> I could work on a new version of the Docbook Tool that would support
> this, if we agree that's the way to go.
>
>
> Best regards,
>
>
> Dirk
>
>
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] should src/engine/SCons/Tool/docbook/util/* be included in the packages?

[Dirk Bächle]

Hi Bill,


Am 07.10.2018 um 21:44 schrieb Bill Deegan:
Are the docbook xslt stylesheets we're currently including reasonably 
available from distro's repos?




I haven't checked yet, but my guess is that some version would be 
offered in the major distros. But the problem is then that different 
naming schemes would be used and the folder with the stylesheets would 
be stored in random locations. This makes it difficult to provide an 
out-of-the-box experience with the Docbook Tool.



I saw today that the actual sources of the Docbook XSLT stylesheets are 
now hosted on github too! This made me think: Maybe it would be okay to 
add another "bootstrapping step" to the Docbook Tool, where it clones 
the stylesheets from github to its local folder?


Then we wouldn't have to store all the XSLT files directly in our repo. 
Our build/release workflow would get a little more complicated and users 
of the Docbook Tool would have to "init" it once on each of their 
machines. But maybe it's worth giving it a try?


I could work on a new version of the Docbook Tool that would support 
this, if we agree that's the way to go.



Best regards,


Dirk



___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] should src/engine/SCons/Tool/docbook/util/* be included in the packages?

[Paweł Tomulik]

Gosh, I was working on 3.0.1 (2017, from Debian repo). I've tried with
master and it seems to work. Sorry for the noise.

W dniu 06.10.2018 o 06:26, Bill Deegan pisze:
> Strange that it's referring to
> "/usr/lib/scons/SCons/Tool/docbook/utils/xmldepend.xsl",  it should be
> referring to build/... for the unpacked version of the package.
> 
> Have you run python bootstrap.py first?
> 
> On Fri, Oct 5, 2018 at 1:35 PM Paweł Tomulik  > wrote:
> 
> The problem still persists:
> 
> I/O warning : failed to load external entity
> "/usr/lib/scons/SCons/Tool/docbook/utils/xmldepend.xsl"
> scons: *** [build/doc/user/manual.fo ] parserError
> : xmlParseFile() failed
> scons: building terminated because of errors.
> 
> should I file an issue on GitHub?
> 
> W dniu 18.09.2017 o 21:45, Bill Deegan pisze:
> > More data: 
> > Here's the failure output when running against package:
> >
> > warning: failed to load external entity
> >
> 
> "/home/bdbaddog/devel/scons/as_scons/build/test-src-tar-gz/lib/scons/SCons/Tool/docbook/utils/xmldepend.xsl"
> > cannot parse
> >
> 
> /home/bdbaddog/devel/scons/as_scons/build/test-src-tar-gz/lib/scons/SCons/Tool/docbook/utils/xmldepend.xsl
> > TypeError: __str__ returned non-string (type NoneType):
> >   File
> >
> 
> "/home/bdbaddog/devel/scons/as_scons/build/test-src-tar-gz/lib/scons/SCons/Script/Main.py",
> > line 1361:
> >     _exec_main(parser, values)
> >   File
> >
> 
> "/home/bdbaddog/devel/scons/as_scons/build/test-src-tar-gz/lib/scons/SCons/Script/Main.py",
> > line 1324:
> >     _main(parser)
> >   File
> >
> 
> "/home/bdbaddog/devel/scons/as_scons/build/test-src-tar-gz/lib/scons/SCons/Script/Main.py",
> > line 1103:
> >     nodes = _build_targets(fs, options, targets, target_top)
> >   File
> >
> 
> "/home/bdbaddog/devel/scons/as_scons/build/test-src-tar-gz/lib/scons/SCons/Script/Main.py",
> > line 1298:
> >     jobs.run(postfunc = jobs_postfunc)
> >   File
> >
> 
> "/home/bdbaddog/devel/scons/as_scons/build/test-src-tar-gz/lib/scons/SCons/Job.py",
> > line 111:
> >     self.job.start()
> >   File
> >
> 
> "/home/bdbaddog/devel/scons/as_scons/build/test-src-tar-gz/lib/scons/SCons/Job.py",
> > line 214:
> >     task.failed()
> >   File
> >
> 
> "/home/bdbaddog/devel/scons/as_scons/build/test-src-tar-gz/lib/scons/SCons/Script/Main.py",
> > line 274:
> >     sys.stderr.write(errfmt % (nodename, buildError))
> >
> >
> > On Mon, Sep 18, 2017 at 3:36 PM, Bill Deegan
> mailto:b...@baddogconsulting.com>
> >  >> wrote:
> >
> >     Dirk,
> >
> >     Looks like it's not currently and when I run "python runtest.py -p
> >     src-tar-gz -a" to run against the generated packages there are
> many
> >     docbook related failures.
> >
> >     Thoughts?
> >
> >     _Bill
> >
> >
> >
> >
> > ___
> > Scons-dev mailing list
> > Scons-dev@scons.org 
> > https://pairlist2.pair.net/mailman/listinfo/scons-dev
> >
> 
> 
> -- 
> Pawel Tomulik
> ___
> Scons-dev mailing list
> Scons-dev@scons.org 
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
> 
> 
> 
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
> 


-- 
Pawel Tomulik
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Help needed for D support in SCons on Windows

[Russel Winder]

On Sun, 2018-10-07 at 10:51 +, rjframe via Digitalmars-d wrote:
[…]
> 
> I don't use SCons, but took a quick look; my current guess is that the 
> problem is the chocolatey installation of dmd and the rest in AppVeyor; 
> chocolatey doesn't install DMD in %SYSTEMROOT% and I don't know if the 
> path updates take effect without restarting the shell (my own PC is too 
> polluted to test this locally).
> 
> Using SCons.Debug.Trace just crashes with "ValueError: I/O operation on 
> closed file.", writing both to stdout and a file, so I haven't been able 
> to test anything.

Thanks for taking a look into it. It seems like Chocolatey is not playing
entirely fair.

-- 
Russel.
===
Dr Russel Winder  t: +44 20 7585 2200
41 Buckmaster Roadm: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk



signature.asc
Description: This is a digitally signed message part
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev