Hi Marc,
    I just did a fresh clone of the master tree from github and ran
autogen.sh and configure and I'm seeing this error:

    sh autogen.sh
    ./configure --with-dfb --with-x=no  --with-xkbfile=no  --with-pulse
    --with-debug=no
    make
    ...

    Making all in libfreerdp-rfx
    make[2]: Entering directory
    `/home/greno/build/test/FreeRDP/libfreerdp-rfx'
      CC     libfreerdp_rfx_la-rfx_bitstream.lo
      CC     libfreerdp_rfx_la-rfx_rlgr.lo
      CC     libfreerdp_rfx_la-rfx_differential.lo
      CC     libfreerdp_rfx_la-rfx_quantization.lo
      CC     libfreerdp_rfx_la-rfx_dwt.lo
      CC     libfreerdp_rfx_la-rfx_decode.lo
      CC     libfreerdp_rfx_la-rfx_pool.lo
      CC     libfreerdp_rfx_la-librfx.lo
    make[2]: *** No rule to make target `sse/libfreerdp-rfx-sse.la',
    needed by `libfreerdp-rfx.la'.  Stop.
    make[2]: Leaving directory
    `/home/greno/build/test/FreeRDP/libfreerdp-rfx'
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/home/greno/build/test/FreeRDP'
    make: *** [all] Error 2


Gerry




On 06/08/2011 04:06 PM, Marc-André Moreau wrote:
> I have already merged Steve's latest work with SSE, cleaned it up, and
> pushed. It is now compiled as a separate module and only linked when
> the --with-sse option is given to the configure script.
>
> On Wed, Jun 8, 2011 at 2:13 PM, Marc-André Moreau
> <marcandre.mor...@gmail.com <mailto:marcandre.mor...@gmail.com>> wrote:
>
>     Hi FreeRDP developers,
>
>     Since we're a bunch of people who want to work on RemoteFX at the
>     same time, I think that working each one on our github forks adds
>     unnecessary overhead. Still, we don't want to be pushing straight
>     on master, since we could be breaking stuff. I will therefore
>     start a new branch on the main FreeRDP git repository and grant
>     access to those working on RemoteFX, such that we can work more
>     quickly.
>
>     I kind of like the github pull request system since it allows to
>     review code as it is written. After creating the new branch, I
>     will start a new pull request such that RemoteFX developers will
>     be able to comment on each other's code, but the branch should
>     only be merged once we bring the code back into a stable state.
>
>     If I understood correctly, people working on RemoteFX so far would
>     be me, Martin, Vic, and Steve. There's a chance that I get someone
>     else involved but then I'll let you know about it.
>
>     I created the new branch here:
>     https://github.com/FreeRDP/FreeRDP/tree/remotefx
>
>     And also a new team:
>     https://github.com/organizations/FreeRDP/teams/63328
>
>     If someone has a better suggestion for how we can proceed, let me
>     know. Creating a new organization looks like a lot of overhead,
>     specially since people who want to work on it are not an
>     organization but different people spread across the world.
>
>
>
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
>   
>
>
> _______________________________________________
> Freerdp-devel mailing list
> Freerdp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freerdp-devel
>   



------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Freerdp-devel mailing list
Freerdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Reply via email to