[wsf-c-dev] TODOs for WSF/C 1.0

[Samisa Abeysinghe]

Sanjaya Ratnaweera wrote:

> Samisa Abeysinghe wrote:
>
>> Sanjaya Ratnaweera wrote:
>>
>>> Hi,
>>>
>>>>
>>>> 6. Fix the build - drop copying makefiles
>>>
>>>
>>> This can be done, but we need to keep Axis2/C, Sandesha2/C, 
>>> Rampart/C, Savan/C in our repository, because since we're building 
>>> them all as a one package we need to edit Makefiles anyway.
>>
>>
>> I am -1 on keeping them inside WSF/C repo - we have to stick with the 
>> extern link. Keeping them inside is going to make matters worse than 
>> copying make files.
>> What we can do is to see if we can copy a minimal set of make files, 
>> rather than copying all. At the moment we copy all of the makefiles. 
>> But I am sure, we can live with some of the make files in source 
>> folders as they are and copy/modify only the wrapper makefiles.
>
> Nope. When we build Sandesha2, Rampart and Savan seperately it expects 
> installed Axis2/C version in our machine. (By default it links 
> libraries from $AXIS2C_HOME/lib). But when we build everything 
> together we need to give relative path to link libraries(Because when 
> 'make' libraries are still not installed). To do it we need to change 
> most of the Makefiles in Sandesha2, Rampart and Savan.

Can we think of some settings, variables or something like that to be 
used in make files. Then instead of hard coded values, we can set those 
variables and let the make system pick from that. Would that be feasible?

Samisa...

>
> Thanks
>
>    ~sanjaya
>
>>
>> Samisa...
>>
>>
>>
>> _______________________________________________
>> Wsf-c-dev mailing list
>> Wsf-c-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/wsf-c-dev
>>
>
>
> _______________________________________________
> Wsf-c-dev mailing list
> Wsf-c-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsf-c-dev
>
>