On Aug 23, 2011, at 4:03 PM, Satish Balay wrote:
> On Tue, 23 Aug 2011, Barry Smith wrote:
>
>>
>> On Aug 23, 2011, at 3:54 PM, Satish Balay wrote:
>>
>>> Perhaps we should pull it out to the toplevel 'matlab' target - which
>>> does this build for both cases?
>>>
>>> i.e
>>>
>>> all:
>>> make all-cmake matlab
>>> or
>>> make all-legacy matlab
>>>
>>> Also: [For Barry] from src/sys/viewer/impls/socket/matlab/makefile
>>>
>>>>>>>>>>>>>
>>> sread:
>>> -@${MATLAB_MEX} -g CC='${PCC}' CFLAGS='${COPTFLAGS} ${CC_FLAGS}
>>> ${CCPPFLAGS}' sread.c bread.c -lc
>>> -@${RM} -f sread.o bread.o
>>> -@${MV} sread.mex* ${PETSC_DIR}/bin/matlab
>>> <<<<<<<,
>>>
>>> Should these binaries be copied over to ${PETSC_DIR}/{PETSC_ARCH}/bin?
>>> [alternatively ${PETSC_DIR}/{PETSC_ARCH}/matlab/bin]
>>
>> No, because MATLAB handles its own multiple arches itself so they can all
>> be dumped in the same directory. And it saves the user mucking with adding
>> yet another path to MATLABPATH.
>
> But dumping generated files in PETSC_ARCH/bin? {PETSC_DIR}/{PETSC_ARCH}/bin
> is more appropriate for generated files.
>
> [we could use this argument for mpiexec,bfort etc - and dump them in
> PETSC_DIR/bin - but we don't]
No, those are all arch specific and if you build with two arches the mpiexec
will overwrite each other.
Plus the generated files do not go in bin they go in bin/matlab
You could argue that we should ONLY ever dump generated files in
$PETSC_ARCH, but I see no harm in this particular one and it makes live easier
for MATLAB users so we do it.
Barry
>
> Satish
>
>
>>
>>
>> Barry
>>
>>>
>>> Satish
>>>
>>>
>>>
>>> On Tue, 23 Aug 2011, Jed Brown wrote:
>>>
>>>> IIRC, that part is basically shell script embedded in the makefile. If we
>>>> make it structured, then the CMake build can do it, otherwise we would have
>>>> to write a custom hack which would duplicate logic.
>>>> On Aug 23, 2011 1:43 PM, "Satish Balay" <balay at mcs.anl.gov> wrote:
>>>>> Jed,
>>>>>
>>>>> Looks like cmake does not do part of the matlab build..
>>>>>
>>>>>>>>>>>
>>>>> libfast in: /sandbox/balay/petsc-dev/src/sys/viewer/impls/socket/matlab
>>>>> BEGINNING TO COMPILE MATLAB INTERFACE
>>>>>
>>>>> Warning: You are using gcc version "4.4.3-4ubuntu5)". The version
>>>>> currently supported with MEX is "4.3.4".
>>>>> For a list of currently supported compilers see:
>>>>> http://www.mathworks.com/support/compilers/current_release/
>>>>>
>>>>>
>>>>> Warning: You are using gcc version "4.4.3-4ubuntu5)". The version
>>>>> currently supported with MEX is "4.3.4".
>>>>> For a list of currently supported compilers see:
>>>>> http://www.mathworks.com/support/compilers/current_release/
>>>>>
>>>>>
>>>>> Warning: You are using gcc version "4.4.3-4ubuntu5)". The version
>>>>> currently supported with MEX is "4.3.4".
>>>>> For a list of currently supported compilers see:
>>>>> http://www.mathworks.com/support/compilers/current_release/
>>>>>
>>>>>
>>>>> Warning: You are using gcc version "4.4.3-4ubuntu5)". The version
>>>>> currently supported with MEX is "4.3.4".
>>>>> For a list of currently supported compilers see:
>>>>> http://www.mathworks.com/support/compilers/current_release/
>>>>>
>>>>> libfast in:
>>>> /sandbox/balay/petsc-dev/src/sys/viewer/impls/socket/ftn-custom
>>>>> <<<<<<<
>>>>>
>>>>> Satish
>>>>>
>>>>
>>>
>>
>>
>
