[FreeNX-kNX] Compiling NX1.5.0 on amd64

LROUFAIL at nc.rr.com LROUFAIL at nc.rr.com
Sat Sep 24 19:12:50 UTC 2005


Nomachine is a company.  They produce native packages for platforms
based on what the market desires.

We are fortunate they don't just create software for Windows like most
commercial software.

We are also fortunate they release their core libraries to GPL so that
the community has the opportunity to provide support for other platforms.

Most of the serious developers on NX technology will say that Nomachine
has been very friendly to the community - even when it clearly has a
negative impact on their own business.

If you want commercial support for your platform, buy a license and then
contact Nomachine and ask about creating a business relationship and
what it would cost.

Don't take potshots at them from a free forum.  They don't owe us better
documentation.  The code is a good enough gift to the community.  If you
want more you should pay for it.


-------------- next part --------------
It's the package that released by NoMachine. Anywhere is it stated that the
files in nx-X11/lib/X11was not written by your people and supposed to be the
same Xlib code of XFree86/X.org distributions?

Your knowledge base is so 'user friendly' that it is short of information
that developers would need. For example, reading through the 'building NX
components' article doesn't solve the compilation problems I met at all.

You know I am not trolling. I have spent several nights on it, and have
reported the compilation attempt at length. I understand that critical words
are hard to digest but if you think this is still trolling I could say
nothing else. No more flamebait, just feel frustrated by the current NX
package. It could only be mitigated after somebody managed to get deb/rpm
package done/patched.

Xiong

On 9/24/05, Gian Filippo Pinzari <pinzari at nomachine.com> wrote:
>
> Xiong Jiang wrote:
> > I am still quite surprised about the package being released in such a
> > shape. Maybe NoMachine is short of resources as well.
>
> Yes, we are short of resources :-). Anyway, did you realize that the code
> you are talking about was not written by us but it is supposed to be the
> same Xlib code of the XFree86/X.org distributions?
>
> Instead of trolling, why don't you spend the time to compare the code with
> the latest XFree86/X.org versions? Maybe the fix (if it was actually a
> bug)
> has been merged in the XFree86/X.org code but not in nx-X11, for example
> because our builds have never come through the same bug.
>
> BTW, I strongly suggest you take a look at the NoMachine KB and at the
> other documents. They explain at length why you should keep the NX libs
> and the native X11 libs in separate directories.
>
> /Gian Filippo.
>
>
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20050924/c198ccb0/attachment.html>
-------------- next part --------------
_______________________________________________
FreeNX-kNX mailing list
FreeNX-kNX at kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx


More information about the FreeNX-kNX mailing list