From: viz <ze...@hm...> - 2007-06-14 23:56:34
|
I have written a package that I would like to be a part of the RVM I'm running. I do not care if it is a part of the RVM conditionally based on a property that needs to be set either at command line or in some file, or is unconditionally added. However, I cannot determine how to cause a build of the RVM to include the package. The package is used by the TraceLocal code inside the RVM, so it is required by any collector that uses tracing. How would I build the RVM including this package? -- View this message in context: http://www.nabble.com/Add-a-package-to-the-RVM-tf3925047.html#a11131021 Sent from the jikesrvm-researchers mailing list archive at Nabble.com. |
From: Peter D. <pe...@re...> - 2007-06-16 00:13:45
|
Hi, On 6/15/07, viz <ze...@hm...> wrote: > > > I have written a package that I would like to be a part of the RVM I'm > running. I do not care if it is a part of the RVM conditionally based on > a > property that needs to be set either at command line or in some file, or > is > unconditionally added. However, I cannot determine how to cause a build > of > the RVM to include the package. The package is used by the TraceLocal > code > inside the RVM, so it is required by any collector that uses tracing. How > would I build the RVM including this package? Theres three things that need to be addressed when including code within the RVM. 1. getting it compiled 2. getting it included in rvm jar 3. getting it included in bootimage for (1) you need to look at build.xml:875 and make sure the path to your source is included there. For (2) look at build.xml:932 to make sure your classes are included there and for (3) look at line 954 to make sure classes included in primordial list. Hope that helps, Peter Donald |
From: viz <ze...@hm...> - 2007-06-18 18:05:53
|
Peter Donald-2 wrote: > > Hi, > > Theres three things that need to be addressed when including code within > the > RVM. > 1. getting it compiled > 2. getting it included in rvm jar > 3. getting it included in bootimage > > for (1) you need to look at build.xml:875 and make sure the path to your > source is included there. For (2) look at build.xml:932 to make sure your > classes are included there and for (3) look at line 954 to make sure > classes > included in primordial list. > > Hope that helps, > > Peter Donald > > I now have a setup so my package will be included in every build of the RVM, thanks. If I wanted to make it optionally included, for example, by requiring the property config.include.package to be set to true to include it, and false otherwise, how would I add the check for that property? Zvi Effron -- View this message in context: http://www.nabble.com/Add-a-package-to-the-RVM-tf3925047.html#a11180939 Sent from the jikesrvm-researchers mailing list archive at Nabble.com. |
From: Peter D. <pe...@re...> - 2007-06-18 18:40:05
|
On 6/19/07, viz <ze...@hm...> wrote: > > I now have a setup so my package will be included in every build of the > RVM, > thanks. If I wanted to make it optionally included, for example, by > requiring the property config.include.package to be set to true to include > it, and false otherwise, how would I add the check for that property? It depends on your particular extension but most likely you would include a boolean value in rvm/src-generated/vm_configuration/VM_Configuration.template that is set by passing in values from build.xml:729, guard all your extra code using this flag and optionally include the new primordial classes in a way similar to how we do it for opt compiler in build.xml:993 -- Cheers, Peter Donald |