Don't set the #[cfg(not(test))] macro in entry_point macro

Author: phil-opp

Changelog.md

@@ -1,3 +1,11 @@
+## Breaking
+
+- Don't set the `#[cfg(not(test))]` attribute for the entry point function in the `entry_point` macro
+    - With custom test frameworks, it's possible to use the normal entry point also in test environments
+    - To get the old behavior, you can add the `#[cfg(not(test))]` attribute to the `entry_point` invocation
+
+## Other
+
 - Additional assertions for the passed `KERNEL` executable
     - check that the executable exists (for better error messages)
     - check that the executable has a non-empty text section (an empty text section occurs when no entry point is set)

src/lib.rs

@@ -22,7 +22,6 @@ pub mod bootinfo;
 #[macro_export]
 macro_rules! entry_point {
     ($path:path) => {
-        #[cfg(not(test))]
         #[export_name = "_start"]
         pub extern "C" fn __impl_start(boot_info: &'static $crate::bootinfo::BootInfo) -> ! {
             // validate the signature of the program entry point