Re: [Mono-dev] github workflow proposals
On Thu, Jul 29, 2010 at 5:44 PM, Geoff Norton wrote: > I think this looks great, but before we can get rid of them we probably need > to integrate this into make dist so that its automatic, so we need some way > of determining the start commit programatically if at all possible. Alright, so I've implemented this as well: http://github.com/schani/mono/commit/89bc1e27704126919891b3219895d1f13cd2f1f9 All that's required now is setting the tag "last-commit-with-compulsory-changelog-entry" and everything should be taken care of automatically. If nobody objects I'll push that to the public repository and never write a ChangeLog entry again. Mark ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] github workflow proposals
On Thu, 2010-07-29 at 11:44 -0400, Geoff Norton wrote: > On 2010-07-29, at 11:29 AM, Mark Probst wrote: > > > On Wed, Jul 28, 2010 at 5:12 PM, Mark Probst wrote: > >> If nobody else does it I'm volunteering - I really, really want to get > >> rid of ChangeLogs :-) > > > > > > These will be put into the corresponding ChangeLog files. If a > > comment specifies files in directories with separate ChangeLogs, the > > comments will be put in each of them, but only with the relevant files > > in the comment. > > > > If there are no comments mentioning files for a particular ChangeLog > > in whose directory some file has been touched, then whatever comes > > before the first per-file comment will be put into that ChangeLog. In > > the extreme case (no per-file comments) that means the whole comment. > > > > Please see the test cases for details. > > > > Comments, suggestions? Is this enough to get rid of ChangeLog entries > > in commits? > > I think this looks great, but before we can get rid of them we probably need > to integrate this into make dist so that its automatic, so we need some way > of determining the start commit programatically if at all possible. > > Thoughts? You can always use http://live.gnome.org/Git/ChangeLog as reference. - Mario ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] CodeDomProvider.CreateProvider fails on Windows
Hey,
On 29.07.2010 18:52, Frank Fuchs wrote:
> Yes I did. otherwise the mono_jit_init wouldn't work, and I was not able to
> start the C# routines.
Yeah, my bad.
I believe the issue is more profane: Mono is trying to launch
gmcs with bin/gmcs.bat, but the latter contains absolute paths
set by the Mono installer => the script is not relocatable.
Change gmcs.bat to look like this:
@"%~dp0\mono.exe" %MONO_OPTIONS% "%~dp0\..\lib\mono\2.0\gmcs.exe" %*
%~dp0 (a cmd.exe variable) is expanded to the actual path of
gmcs.bat, making the script relocatable.
Robert
> However, this works well also for rather complicated routines interacting
> with the host-app.
> The specific c# programm exits at the CodeDomProvider.CreateProvider call.
>
> -Frank
>
>
>> Date: Thu, 29 Jul 2010 11:22:24 +0200
>> From: Robert Jordan
>> Subject: Re: [Mono-dev] CodeDomProvider.CreateProvider fails on
>> Windows
>> To: mono-devel-list@lists.ximian.com
>> Message-ID:
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> On 29.07.2010 09:25, Frank Fuchs wrote:
>>> Hi,
>>>
>>> I'd like to compile .cs files at runtime. Following the tip frome here
>>> http://lists.ximian.com/pipermail/mono-devel-list/2010-July/035505.html I'm
>>> able to do that on my Mac. On Windows (win 7 enterprise) however I do not
>>> manage to get it running.
>>> The program exits with exit code 01 right when calling
>>> CodeDomProvider.CreateProvider("C#"). I'm using mono in a relocated setup
>>> (no admin rights on the windows machine).
>>> Strangely the program executes well when I call the assembly with mono from
>>> command line, but fails when calling it from the embedding c++ application
>>
>> Are you calling mono_set_dirs() [1] from C++?
>>
>> Mono for Windows needs this call because libmono cannot detect
>> relocations under Windows.
>>
>> Robert
>>
>> [1] http://preview.tinyurl.com/39d57tg
>
>
>
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] CodeDomProvider.CreateProvider fails on Windows
Yes I did. otherwise the mono_jit_init wouldn't work, and I was not able to
start the C# routines.
However, this works well also for rather complicated routines interacting with
the host-app.
The specific c# programm exits at the CodeDomProvider.CreateProvider call.
-Frank
> Date: Thu, 29 Jul 2010 11:22:24 +0200
> From: Robert Jordan
> Subject: Re: [Mono-dev] CodeDomProvider.CreateProvider fails on
> Windows
> To: mono-devel-list@lists.ximian.com
> Message-ID:
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 29.07.2010 09:25, Frank Fuchs wrote:
>> Hi,
>>
>> I'd like to compile .cs files at runtime. Following the tip frome here
>> http://lists.ximian.com/pipermail/mono-devel-list/2010-July/035505.html I'm
>> able to do that on my Mac. On Windows (win 7 enterprise) however I do not
>> manage to get it running.
>> The program exits with exit code 01 right when calling
>> CodeDomProvider.CreateProvider("C#"). I'm using mono in a relocated setup
>> (no admin rights on the windows machine).
>> Strangely the program executes well when I call the assembly with mono from
>> command line, but fails when calling it from the embedding c++ application
>
> Are you calling mono_set_dirs() [1] from C++?
>
> Mono for Windows needs this call because libmono cannot detect
> relocations under Windows.
>
> Robert
>
> [1] http://preview.tinyurl.com/39d57tg
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] commit-to-changelog script (was Re: github workflow proposals)
On Thu, Jul 29, 2010 at 6:00 PM, Raja R Harinath wrote: > We can choose a flag day, say this weekend, when we stop adding > ChangeLogs. The script already seems to handle stray ChangeLog updates, > but it can trim the history it needs to scan by using > > git log --no-merges --all --since 2010-08-01 > > or something like that. The script is given a commit after which to start processing. So if we just add a tag "last-changelog" then we can call the script from "make dist" with that argument. Should we at some point decide to commit all those generated ChangeLog entries we can just reset the tag to that commit. Mark ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] commit-to-changelog script (was Re: github workflow proposals)
Hi, Geoff Norton writes: > On 2010-07-29, at 11:29 AM, Mark Probst wrote: [snip] >> Comments, suggestions? Is this enough to get rid of ChangeLog entries >> in commits? > > I think this looks great, but before we can get rid of them we > probably need to integrate this into make dist so that its automatic, > so we need some way of determining the start commit programatically if > at all possible. We can choose a flag day, say this weekend, when we stop adding ChangeLogs. The script already seems to handle stray ChangeLog updates, but it can trim the history it needs to scan by using git log --no-merges --all --since 2010-08-01 or something like that. - Hari ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Ximian-mono-list] github workflow proposals
On Thu, Jul 29, 2010 at 5:49 PM, Raja R Harinath wrote: > What happens if I use a directory prefix? Additional log information? http://github.com/schani/mono/commit/3132fb81d52bc31446e856e6e14f44e8e80f0f36 Mark ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Ximian-mono-list] github workflow proposals
Hi, On Thu, Jul 29, 2010 at 20:59, Mark Probst wrote: > You can write per-file comments like so: > > --- > * sgen-gc.c: Whatever. > --- > > Or, more elaborately: > > --- > * sgen-gc.c (major_do_collection), sgen-gc.h: Something. > --- What happens if I use a directory prefix? Additional log information? Description of whole change And some rationale, which goes on and on for a few more lines. ... * metadata/sgen-gc.c: Some changes. * mini/main.c: Some other changes. - Hari ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] github workflow proposals
On 2010-07-29, at 11:29 AM, Mark Probst wrote: > On Wed, Jul 28, 2010 at 5:12 PM, Mark Probst wrote: >> If nobody else does it I'm volunteering - I really, really want to get >> rid of ChangeLogs :-) > > These will be put into the corresponding ChangeLog files. If a > comment specifies files in directories with separate ChangeLogs, the > comments will be put in each of them, but only with the relevant files > in the comment. > > If there are no comments mentioning files for a particular ChangeLog > in whose directory some file has been touched, then whatever comes > before the first per-file comment will be put into that ChangeLog. In > the extreme case (no per-file comments) that means the whole comment. > > Please see the test cases for details. > > Comments, suggestions? Is this enough to get rid of ChangeLog entries > in commits? I think this looks great, but before we can get rid of them we probably need to integrate this into make dist so that its automatic, so we need some way of determining the start commit programatically if at all possible. Thoughts? -g ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Git faq updated with workflows
Hi, "pablosantosl...@terra.es" writes: > On 29/07/2010 3:52, Andreia Gaita wrote: >> I've added a couple of simple workflows to our git faq, >> http://www.mono-project.com/GitFAQ#Workflow . See if these work for >> you, they should make it easier to avoid merge commits. There are >> plenty of ways to do things, and these don't include working on forks, >> although it's not too different. More to come later, opinions welcome. > > I'd strongly recommend you separate every task (every entry on bugzilla) > on a separated branch. Yep. However, I don't think we want to mandate such major changes in workflow right now. I've updated the workflow information above to start moving us along towards the workflow you mention. The good part of your recommended workflow is that each of us can adopt it at our own pace, and improve our productivity, without waiting for others to pick up on it immediately. Of course, project-wide quality accelerators like git-bisect will only work well once a lot more of us adopt the workflow. - Hari ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] github workflow proposals
On Wed, Jul 28, 2010 at 5:12 PM, Mark Probst wrote: > If nobody else does it I'm volunteering - I really, really want to get > rid of ChangeLogs :-) And here is the script: http://github.com/schani/mono/tree/commit-to-changelog Here are a few test cases: http://github.com/schani/mono/commits/commit-to-changelog-tests It works like this: The script will add ChangeLog entries for all files that a commit touches. All commits that touch any ChangeLog file are ignored. You can write per-file comments like so: --- * sgen-gc.c: Whatever. --- Or, more elaborately: --- * sgen-gc.c (major_do_collection), sgen-gc.h: Something. --- These will be put into the corresponding ChangeLog files. If a comment specifies files in directories with separate ChangeLogs, the comments will be put in each of them, but only with the relevant files in the comment. If there are no comments mentioning files for a particular ChangeLog in whose directory some file has been touched, then whatever comes before the first per-file comment will be put into that ChangeLog. In the extreme case (no per-file comments) that means the whole comment. Please see the test cases for details. Comments, suggestions? Is this enough to get rid of ChangeLog entries in commits? Mark ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] App needs Regex.CompileToAssembly method
On Wed, Jul 28, 2010 at 12:40 PM, scope_creep wrote: > > > I'm porting an app and ran the migration wizard. Found a MonoTodo, and > subsequently found that > System.Text.RegularExpresssions.Regex.CompileToAssembly method is currently > not implemented. > > The app used it pretty extensively to speed up regex pattern matching. How > would I find out if this method will be implemented, or when. > > Thanks. > > Bob. > We have no defined plan to support compiled regexps. You can contribute support for them thou. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Git faq updated with workflows
All, I'd strongly recommend you separate every task (every entry on bugzilla) on a separated branch. I'm very used to it since this is the way we work internally in Plastic (and what we do recommend to all our customers). It gives you perfect traceability and flexibility to handle all changes. Git is perfectly capable of handling high number of branches (as plastic is too, something you didn't have with SVN), so I think this one is a perfect solution. Basically it means: you'll be using branches instead of "commits" as "unit of change". Hope it helps, pablo On 29/07/2010 3:52, Andreia Gaita wrote: > I've added a couple of simple workflows to our git faq, > http://www.mono-project.com/GitFAQ#Workflow . See if these work for > you, they should make it easier to avoid merge commits. There are > plenty of ways to do things, and these don't include working on forks, > although it's not too different. More to come later, opinions welcome. > > andreia gaita > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] CodeDomProvider.CreateProvider fails on Windows
On 29.07.2010 09:25, Frank Fuchs wrote:
> Hi,
>
> I'd like to compile .cs files at runtime. Following the tip frome here
> http://lists.ximian.com/pipermail/mono-devel-list/2010-July/035505.html I'm
> able to do that on my Mac. On Windows (win 7 enterprise) however I do not
> manage to get it running.
> The program exits with exit code 01 right when calling
> CodeDomProvider.CreateProvider("C#"). I'm using mono in a relocated setup
> (no admin rights on the windows machine).
> Strangely the program executes well when I call the assembly with mono from
> command line, but fails when calling it from the embedding c++ application
Are you calling mono_set_dirs() [1] from C++?
Mono for Windows needs this call because libmono cannot detect
relocations under Windows.
Robert
[1] http://preview.tinyurl.com/39d57tg
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] CodeDomProvider.CreateProvider fails on Windows
Hi,
I'd like to compile .cs files at runtime. Following the tip frome here
http://lists.ximian.com/pipermail/mono-devel-list/2010-July/035505.html I'm
able to do that on my Mac. On Windows (win 7 enterprise) however I do not
manage to get it running.
The program exits with exit code 01 right when calling
CodeDomProvider.CreateProvider("C#"). I'm using mono in a relocated setup
(no admin rights on the windows machine).
Strangely the program executes well when I call the assembly with mono from
command line, but fails when calling it from the embedding c++ application
(other calls from this app work well on windows and the mac). Sadly I do not
get any output apart form the exit code, even when using gdb.
Am I missing any initializations? Do I need to tell the program where the
compiler is?
-Frank
using System;
using System.IO;
using System.Runtime.InteropServices;
using System.Runtime.CompilerServices;
using System.CodeDom.Compiler;
using System.Reflection;
namespace MonoCSharpCompiler
{
class Compiler
{
public static void Main ()
{
string[] rFileNames=new string[2];
rFileNames[0]="D:\\ScriptTests\\Mono\\auto.cs";
rFileNames[1]="D:\\ScriptTests\\Mono\\MonoScriptGlue.cs";
CodeDomProvider provider = CodeDomProvider.CreateProvider
("C#"); // <<< IT FAILS HERE
CompilerParameters parms = new CompilerParameters ();
parms.GenerateExecutable = true;
parms.OutputAssembly =
Path.ChangeExtension(rFileNames[0],".exe");
Console.WriteLine(parms.OutputAssembly);
CompilerResults cr=provider.CompileAssemblyFromFile(parms,
rFileNames);
// If errors occurred during compilation, output the compiler
output and errors.
Console.WriteLine( "Compiler returned with result code: " +
cr.NativeCompilerReturnValue.ToString() );
foreach ( Object obj in cr.Output )
Console.WriteLine( ">{0}", obj );
Console.WriteLine("");
if( cr.Errors.Count > 0 )
{
for( int i=0; i___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
