[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-distro-pkg-dev
Subject:    VisualVM in IcedTea6
From:       jsumali () redhat ! com (Joshua Sumali)
Date:       2008-07-30 14:04:37
Message-ID: 489074F5.4070503 () redhat ! com
[Download RAW message or body]

Andrew John Hughes wrote:
> 2008/7/30 Joshua Sumali <jsumali at redhat.com>:
>   
>> Andrew John Hughes wrote:
>>     
>>> 2008/7/30 Joshua Sumali <jsumali at redhat.com>:
>>>
>>>       
>>>> Andrew John Hughes wrote:
>>>>
>>>>         
>>>>> 2008/7/30 Matthias Klose <doko at ubuntu.com>:
>>>>>
>>>>>
>>>>>           
>>>>>> Joshua Sumali schrieb:
>>>>>>
>>>>>>
>>>>>>             
>>>>>>> Hi,
>>>>>>>
>>>>>>> VisualVM is now buildable with IcedTea6 on 32 and 64 bit arch by
>>>>>>> passing
>>>>>>> --enable-visualvm to configure. Details and screenshots can be found
>>>>>>> at
>>>>>>> http://jsumali.wordpress.com/2008/07/29/visualvm-in-icedtea/
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>> Thanks for preparing this. Is there an advantage of building this as
>>>>>> part
>>>>>> of
>>>>>> IcedTea? From a first look the build seems to be independent from
>>>>>> building
>>>>>> "core" IcedTea. It delays the build, increases the source code size,
>>>>>> and
>>>>>> adds
>>>>>> the burden to review licenses for another 30MB compressed source code.
>>>>>> Does the
>>>>>> IcedTea project have to have just one product to deliver, or could this
>>>>>> be
>>>>>> splitted out into a second delivery?
>>>>>>
>>>>>>  Matthias
>>>>>>
>>>>>>
>>>>>>
>>>>>>             
>>>>> Have to say I wondered what was going on when I saw the ChangeLog entry,
>>>>> and I still don't understand the reasoning.  Is there a reason this
>>>>> has to be built WITH the
>>>>> VM?  If it's a truly separate application, then building them against
>>>>> each other is a job
>>>>> for a distro.  Otherwise, the next logical step is --with-eclipse,
>>>>> --with-jboss, --with-glassfish, etc.
>>>>>
>>>>>
>>>>>           
>>>> I should've written better instructions :)
>>>>
>>>> Building visualvm can be done with a simple `make visualvm`. It would
>>>> require an icedtea-ecj build or a precompiled openjdk (--with-openjdk
>>>> passed
>>>> to configure) to build with, but it definitely does not need to build
>>>> IcedTea along with it.
>>>>
>>>> Sorry for the confusion.
>>>> Josh
>>>>
>>>>
>>>>         
>>> So am I right in thinking:
>>>
>>> ./configure <options>
>>> make
>>> make visualvm
>>>
>>> would get me an OpenJDK build with visualvm in j2sdk-image/bin?
>>>
>>>       
>> No, it would only build netbeans7, platform2, and visualvm. The actual
>> "dropping-in" of visualvm occurs right after IcedTea is built. It happens at
>> the same time as the dropping in of gcjwebplugin/icedteaplugin
>> (stamps/icedtea.stamp target in Makefile.am).
>>
>> Josh
>>
>>     
>
> So just ./configure and make will do? with the visualvm option obviously.
>
>   
Yes, this is correct.


[prev in list] [next in list] [prev in thread] [next in thread]