search

devshift / jnativehook

Automatically exported from code.google.com/p/jnativehook
0 stars 0 forks source link

Build failed #41

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.unzip the JNativeHook-src-1.1.3.zip
2.type "ant" under JNativeHook folder 

What is the expected output? What do you see instead?
It just tell me "BUILD FAILED"

What version of the product are you using? On what operating system?
version 1.1.3
Red Hat Enterprise Linux Server release 5.6 (Tikanga)

Please provide any additional information below.

Original issue reported on code.google.com by r...@atso.com.tw on 12 Mar 2013 at 9:49

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by r...@atso.com.tw on 12 Mar 2013 at 9:53

Attachments:

GoogleCodeExporter commented 9 years ago 
What version of GCC?

Original comment by a...@1stleg.com on 12 Mar 2013 at 3:18

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
It sounds like you are using GCC 3.X which is unsupported.  If you can, upgrade 
to GCC 4.X.  If you must use GCC 3.X you can remove -Werror form native.cc.args 
to get it to compile.  You may want to try adding -fno-strict-aliasing instead 
of removing Werror.  I have not extensively tested either option so if you 
choose to use GCC 3.X you will be on your own.

Original comment by a...@1stleg.com on 12 Mar 2013 at 4:27

GoogleCodeExporter commented 9 years ago 
gcc version is 4.1.2

By adding -fno-strict-aliasing,it can be compiled successfully.
Thank you.

Original comment by r...@atso.com.tw on 13 Mar 2013 at 7:35

GoogleCodeExporter commented 9 years ago 
I want to use the hook to avoid some system button (eq. Alt+tab or Alt+Esc) 
making something outside my program. Could you help me?

Original comment by r...@atso.com.tw on 13 Mar 2013 at 7:50

GoogleCodeExporter commented 9 years ago 
Are you trying to ignore these events on your system?  If that is the case, it 
is not possible in a portable way.  See Bug #22 for more information.

Original comment by a...@1stleg.com on 13 Mar 2013 at 10:32

GoogleCodeExporter commented 9 years ago 
I have added -fno-strict-aliasing as a default compile option for all systems.  
This should resolve your starting with r699.

Original comment by a...@1stleg.com on 14 Mar 2013 at 6:58